grpc · Traefik · published 2026-03-20
CVE-2026-33186gRPC-Go has an authorization bypass via missing leading slash in :path
This week Critical (CVSS 9.1) automatable flaw in an edge product.
CVE-2026-33186 is not known to be exploited in the wild. EPSS estimates a 1.7% chance of exploitation in the next 30 days, higher than 78% of all CVEs. This Traefik vulnerability: CVSS 9.1 (v3.1), attacks can be automated. Fixed upstream in Traefik 3.7.0-ea.3, 3.7.0-ea.2, 3.6.12, 3.6.11 (+1 more); patched packages are out for Red Hat Enterprise Linux; Ubuntu and Red Hat Enterprise Linux still have unfixed releases. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Traefik 3.7.0-ea.3, 3.7.0-ea.2, 3.6.12, 3.6.11, 2.11.42.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | golang-google-grpc | Won’t fix |
| 12 bookworm | golang-google-grpc | Won’t fix | |
| Ubuntu (+3 more packages) | 26.04 LTS | golang-google-grpc | No fix yet |
| 22.04 LTS | golang-google-grpc | No fix yet | |
| 20.04 LTS | golang-google-grpc | No fix yet | |
| 18.04 LTS | golang-google-grpc | No fix yet | |
| 16.04 LTS | golang-google-grpc | No fix yet | |
| Red Hat Enterprise Linux (+28 more packages) | RHEL 10 | bootc-image-builder | Won’t fix |
| RHEL 10 | buildah | Not affected | |
| RHEL 10 | grafana | Not affected | |
| RHEL 10 | grafana-pcp | Not affected | |
| RHEL 10 | ignition | No fix yet | |
| RHEL 10 | image-builder | Fixed in 52.1-1.el10_2 RHSA-2026:22937 | |
| RHEL 10 | opentelemetry-collector | Fixed in 0.144.0-2.el10_2 RHSA-2026:19135 | |
| RHEL 10 | osbuild-composer | Fixed in 165.1-2.el10_2 RHSA-2026:22450 |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Web serverTraefik
Traefik security releases: 3.7.0-ea.3, 3.7.0-ea.2, 3.6.12, 3.6.11, 2.11.42
Upgrade to
3.7.0-ea.33.7.0-ea.23.6.123.6.112.11.42Why: CVE-2026-33186: Critical (CVSS 9.1) automatable flaw in an edge product.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.7% (78th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.1 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- grpc grpc-go
< 1.79.3(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.