Is this vulnerability remotely exploitable?

Yes. If a gRPC-Go server is reachable over the network and accepts direct HTTP/2 connections, an attacker with a suitable client can craft requests with non-canonical `:path` values to attempt to bypass path-based authorization policies.

What level of access does an attacker need to exploit this?

The attacker needs network access to the gRPC endpoint and the ability to send low-level HTTP/2 requests, including arbitrary `:path` headers. No prior authentication is required beyond whatever the vulnerable service itself enforces.

What is the safest general fix pattern for affected applications?

The safest pattern is to ensure all requests are validated or normalized before any authorization logic runs. This includes rejecting paths that do not conform to canonical gRPC method format and making sure that both routing and authorization use the same canonical representation when making decisions.

Severity:

CRITICAL RISK

(9.1)

Authorization Bypass via Non-Canonical gRPC Paths (CWE-285) in gRPC-Go Servers

CVE-2026-33186

Published:

Mar 20, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Authorization Bypass

CWE:

CWE-285

Impact:

Unauthorized Access to gRPC Methods

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Authorization Bypass

CWE:

CWE-285

Impact:

Unauthorized Access to gRPC Methods

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Authorization Bypass via Non-Canonical gRPC Paths (CWE-285) in gRPC-Go Servers

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal