GHSA-p77j-4mvh-x3m3 · 深刻度： critical · エコシステム： go — gRPC-Go has an authorization bypass via missing leading slash in :path
gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.
総合評価: CVE-2026-33186 は中リスク（62.7/100）。CVSS 深刻度は重大。悪用される可能性が高い（EPSS 1.56%、72 パーセンタイル） 根拠: 直近 1 日で EPSS が +1.04% 上昇。悪用への関心が高まっている可能性があります。 推奨対応: 影響資産を整理し、修補計画に組み込んでください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-06-30 | 0.52% | 1.56% | +1.04% |
| 2 | 2026-06-15 | 0.01% | 0.52% | +0.51% |
| 3 | 2026-03-21 | — | 0.01% | — |
EPSS の全履歴 （全 3 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 9.1 | 3.1 | CRITICAL |
|
3.9 | 5.2 | [email protected] |
| 9.1 | 3.1 | CRITICAL |
|
3.9 | 5.2 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c |
GHSA-p77j-4mvh-x3m3 · 深刻度： critical · エコシステム： go — gRPC-Go has an authorization bypass via missing leading slash in :path
| vendor | priority | summary | link |
|---|---|---|---|
alpine
|
— | CVE-2026-33186: 1 source package rows (grpc); 19 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 19. | https://security.alpinelinux.org/vuln/CVE-2026-33186 |
debian
|
not yet assigned | CVE-2026-33186 not yet assigned priority: Debian including 1 source packages (golang-google-grpc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. | https://security-tracker.debian.org/tracker/CVE-2026-33186 |
redhat
|
high | — | https://access.redhat.com/security/cve/CVE-2026-33186 |
suse
|
high | CVE-2026-33186 severity important: SUSE including 367 source package names (amazon-cloudwatch-agent-1.300064.0-2.1, amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, …), 662 product×package rows across 38 product lines (Image SLES12-SP5-GCE-SAP-BYOS, Image SLES12-SP5-GCE-SAP-On-Demand, … (38 product lines)): Known Not Affected 296, Known Affected 231, Fixed 66, Will Not Fix 53, First Fixed 16. | https://www.suse.com/security/cve/CVE-2026-33186/ |
ubuntu
|
high | CVE-2026-33186 high priority: Ubuntu including 2 source packages (golang-google-grpc, google-guest-agent), 14 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): needs-triage 14. | https://ubuntu.com/security/CVE-2026-33186 |