BIT-envoy-2026-73552

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/envoy/BIT-envoy-2026-73552.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-envoy-2026-73552
Aliases
Published
2026-09-29T08:43:17Z
Modified
2026-09-29T10:10:44Z
Summary
Envoy: HTTP RBAC safe_regex can fail open on RFC-valid obs-text header values
Details

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.

Database specific 
{
    "cpes":  [
        "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*"
    ],
    "severity":  "High"
}
References

Affected packages

Bitnami / envoy

Package

Name
envoy
Purl
pkg:bitnami/envoy

Severity

  • 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
1.36.10
Introduced
1.37.0
Fixed
1.37.6
Introduced
1.38.0
Fixed
1.38.4
Introduced
1.39.0
Fixed
1.39.1

Database specific

source 
"https://github.com/bitnami/vulndb/tree/main/data/envoy/BIT-envoy-2026-73552.json"