CVE-2026-73551

mediumpriority · track · 0EPSS 0.005 · 44 %ileUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.53% (44th) EPSS

CVSS 5.3 · medium

Is it mine?

8 products

Check your exposure

Who says so?

2 sources

osv · nvd

EPSS · scored 2026-10-27

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.

cvss

Technical severity, 0–10. One row per scoring source.

5.3

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · security-advisories@github.comexploitability 3.9 · impact 1.4

v3.14.9mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-647US

affected products (8)

Products and version ranges known to be affected.

envoyproxy envoy< 1.36.10nvdUScpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
envoyproxy envoy1.37.0 → 1.37.6nvdUScpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
envoyproxy envoy1.38.0 → 1.38.4nvdUScpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
envoyproxy envoy1.39.0 → 1.39.1nvdUScpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
Bitnami envoy< 1.36.10osvUSpkg:bitnami/envoy
Bitnami envoy1.37.0 → 1.37.6osvUSpkg:bitnami/envoy
Bitnami envoy1.38.0 → 1.38.4osvUSpkg:bitnami/envoy
Bitnami envoy1.39.0 → 1.39.1osvUSpkg:bitnami/envoy

advisories (1)

Vendor and ecosystem advisories describing this.

BIT-envoy-2026-73551Envoy: Path normalization does not handle dot and dotdot segments with parameters2026-09-29vendor · osvUS
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.

also known as (1)

Other names and identifiers for this entity.

GHSA-2w8w-rfw7-8gg4 osv

sources

Which sources assert this record, and when.

osv nvd NVD CVE.org MITRE

published 2026-09-21modified 2026-10-05

references (9) nvd

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan