Skip to content
major vulnerability· requires attention

Widespread gRPC-Go library with path-based auth bypass could enable unauthorized RPC access across services; high impact and newsworthy.

Infrastructure

CVE-2026-33186

9.1
Critical
EPSS 2%Patch availableMar 21, 2026

Critical auth bypass in gRPC-Go before 1.79.3 via non-canonical :path header.

common questions

Is CVE-2026-33186 being exploited?

Not confirmed. CVE-2026-33186 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.6% probability of exploitation in the next 30 days.

How severe is CVE-2026-33186?

CVE-2026-33186 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-33186?

Yes. A fix has been recorded for CVE-2026-33186. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-33186 affect?

CVE-2026-33186 affects gRPC-Go servers (google.golang.org/grpc) using path-based auth interceptors. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33186?

Upgrade to 1.79.3+ and enable path normalization/validating interceptors

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
gRPC-Go servers (google.golang.org/grpc) using path-based auth interceptors
impact

Remote authorization bypass; attacker can bypass deny rules and access protected RPCs via crafted HTTP/2 frames.

action required

Patch when possible

affected versions
grpc grpc-go
  • affected< 1.79.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free