CVE-2026-73551: Envoy is an open source edge and service proxy designed for cloud-native applications.

Medium CVSS 5.3

CVE id
CVE-2026-73551
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Envoy
Runtimes and servers
< 1.36.10
>= 1.37.0, < 1.37.6
>= 1.38.0, < 1.38.4
>= 1.39.0, < 1.39.1
1.36.10, 1.37.6, 1.38.4, 1.39.1

How to fix it

Upgrade Envoy to the fixed release of the line you run: 1.36.10, 1.37.6, 1.38.4, 1.39.1.

envoy --version
  • Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.