Back to CVE records
Medium 6.5Published Dec 3, 2025

CVE-2025-64527Envoy is a high-performance edge/middle/service proxy.

Updated under an hour ago ()

Does this affect you?

It affects envoyproxy envoy. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-476
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Sep 25, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
envoyproxy envoy
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
NVD

References

  • exploit, vendor-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.