What’s Vulnerable › Vulnerabilities
CVE-2025-64527: Envoy crashes when JWT authentication is configured with the remote JWKS fetching
- Severity: medium (CVSS 6.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.5% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2025-12-03 · updated 2026-09-25
- Weakness: CWE-476
Description
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, allow_missing_or_failed 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.
Affected products
- envoyproxy envoy: before 1.33.13; from 1.34.0 before 1.34.11; from 1.35.0 before 1.35.7; from 1.36.0 before 1.36.3 — fixed in 1.33.13, 1.34.11, 1.35.7, 1.36.3
How to fix
Upgrade to a fixed version: envoyproxy envoy 1.33.13, 1.34.11, 1.35.7, 1.36.3. Check the vendor advisory for mitigations.
References
Get alerted when CVE-2025-64527 or the next vulnerability affects your stack