CVE-2026-73552

Envoy: HTTP RBAC safe_regex can fail open on RFC-valid obs-text header values

HIGH
7.5
CVSS Score
Published: September 21, 2026 at 07:37 PM UTC
Updated: October 5, 2026 at 02:35 PM UTC
1 product affected across 1 vendorEnvoy

Using envoy by envoyproxy?

Get instant alerts when new vulnerabilities affect envoy - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy HTTP RBAC accepts RFC-valid opaque header bytes but evaluates safe_regex values with RE2's UTF-8 subject semantics. A downstream client can preserve a prohibited marker and add an unrelated obs-text octet, causing RE2::FullMatch to return false and a negative RBAC policy to treat the invalid subject as an ordinary no-match. A byte-oriented route matcher can still observe the marker, allowing the request to reach a route intended to be denied. The relevant scope boundary is that plain positive ALLOW regexes normally fail closed, and exact, prefix, suffix, and contains matchers are not shown to have this subject-domain failure. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.36.10v < 1.37.6v < 1.38.4v < 1.39.11.37.0 ≤ v < 1.37.61.38.0 ≤ v < 1.38.41.39.0 ≤ v < 1.39.1
Affected range stops below 1.36.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.37.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.38.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.39.1, so it looks safe — our inference, not a vendor statement

References (9)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card