envoyproxy · Envoy · published 2026-09-21
CVE-2026-73552Envoy: HTTP RBAC safe_regex can fail open on RFC-valid obs-text header values
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-73552 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 43% of all CVEs. This Envoy vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Envoy 1.39.1, 1.38.4, 1.37.6, 1.36.10.
Patch events
Web serverEnvoy
Envoy security releases: 1.39.1, 1.38.4, 1.37.6, 1.36.10
Upgrade to
1.39.11.38.41.37.61.36.10Why: CVE-2026-73512: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (43th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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)#
- envoyproxy envoy
< 1.36.10(affected)>= 1.37.0, < 1.37.6(affected)>= 1.38.0, < 1.38.4(affected)>= 1.39.0, < 1.39.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.