<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 22:02:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-64527 — Envoy crashes when JWT authentication is configured with the remote JWKS fetching</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-64527</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; envoyproxy envoy&lt;/p&gt;
&lt;p&gt;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&amp;#39;s JWKS fetch fails, onJwksError() callback triggers processing of the second token, which calls fetch() again on the same fetcher object. The original callback&amp;#39;s reset() then clears the second fetch&amp;#39;s state (receiver_ and request_) which causes a crash when the async HTTP response arrives.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; envoyproxy envoy&lt;/p&gt;
&lt;p&gt;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&amp;#39;s JWKS fetch fails, onJwksError() callback triggers processing of the second token, which calls fetch() again on the same fetcher object. The original callback&amp;#39;s reset() then clears the second fetch&amp;#39;s state (receiver_ and request_) which causes a crash when the async HTTP response arrives.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-64527</guid>
    </item>
  </channel>
</rss>
