BIT-envoy-2026-73551

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/envoy/BIT-envoy-2026-73551.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-envoy-2026-73551
Aliases
Published
2026-09-29T08:43:16Z
Modified
2026-09-29T10:10:50Z
Summary
Envoy: Path normalization does not handle dot and dotdot segments with parameters
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's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. 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":  "Medium"
}
References

Affected packages

Bitnami / envoy

Package

Name
envoy
Purl
pkg:bitnami/envoy

Severity

  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-73551.json"