CVE-2025-64527: Envoy is a high-performance edge/middle/service proxy.
Medium CVSS 6.5
- CVE id
- CVE-2025-64527
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
< 1.33.13 >= 1.34.0, < 1.34.11 >= 1.35.0, < 1.35.7 >= 1.36.0, < 1.36.3 |
1.33.13, 1.34.11, 1.35.7, 1.36.3 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.33.13, 1.34.11, 1.35.7, 1.36.3.
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 a high-performance edge/middle/service proxy. In 1.33.12, 1.34.10, 1.35.6, 1.36.2, and earlier, Envoy crashes when JWT authentication is configured with the remote JWKS fetching, allowmissingorfailed is enabled, multiple JWT tokens are present in the request headers and the JWKS fetch fails. This is caused by a re-entry bug in the JwksFetcherImpl. When the first token's JWKS fetch fails, onJwksError() callback triggers processing of the second token, which calls fetch() again on the same fetcher object. The original callback's reset() then clears the second fetch's state (receiver and request_) which causes a crash when the async HTTP response arrives.
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.
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.