Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Envoy (github.com/envoyproxy/envoy) versions before 1.9.1 do not normalize HTTP URL paths. A remote attacker can send a path containing relative segments, such as one that resolves to an admin path, to get past an access control rule on that path, and a backend that interprets the path differently may then grant access beyond what the policy intended. Upgrade to Envoy 1.9.1 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.0 | CVSS:3.0/AC:H/AV:N/A:L/C:L/I:L/PR:N/S:C/UI:N | CNA (mitre) |
- CISA KEV Not listed.
- EPSS 0.050, the 92nd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:45 UTC First seen by agentprime
- 31 Oct 2026, 14:45 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2wmf-p7f8-w42h
- OSV: GHSA-2wmf-p7f8-w42h
- github.com/envoyproxy/envoy/security/advisories/GHSA-xcx5-93pw-jw2w
- nvd.nist.gov/vuln/detail/CVE-2019-9901
- github.com/envoyproxy/envoy/issues/6435
- github.com/envoyproxy/envoy/commit/e668e669677e52a00d99652b5a260d1cedafdfa8
- github.com/envoyproxy/envoy
- github.com/envoyproxy/envoy/blob/main/security/postmortems/cve-2019-9900.md
- groups.google.com/forum/#!topic/envoy-announce/VoHfnDqZiAM
- www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history