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.

Share this

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.

DistroReleasePackageStatus
Debian13 trixiegolang-google-grpcWon’t fix
12 bookwormgolang-google-grpcWon’t fix
Ubuntu (+3 more packages)26.04 LTSgolang-google-grpcNo fix yet
22.04 LTSgolang-google-grpcNo fix yet
20.04 LTSgolang-google-grpcNo fix yet
18.04 LTSgolang-google-grpcNo fix yet
16.04 LTSgolang-google-grpcNo fix yet
Red Hat Enterprise Linux (+28 more packages)RHEL 10bootc-image-builderWon’t fix
RHEL 10buildahNot affected
RHEL 10grafanaNot affected
RHEL 10grafana-pcpNot affected
RHEL 10ignitionNo fix yet
RHEL 10image-builderFixed in 52.1-1.el10_2 RHSA-2026:22937
RHEL 10opentelemetry-collectorFixed in 0.144.0-2.el10_2 RHSA-2026:19135
RHEL 10osbuild-composerFixed 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

  1. This weekSecurity release

    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.42

    Why: CVE-2026-33186: Critical (CVSS 9.1) automatable flaw in an edge product.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)1.7% (78th pct)FIRST EPSS v2026.06.15
CVSS base score9.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 exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

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.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →