<?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>Sun, 22 Nov 2026 23:52:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407362</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407362</link>
      <description>EUVD-2026-407362</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407362</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80322</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80322</link>
      <description>&lt;p&gt;Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80322</guid>
    </item>
    <item>
      <title>GHSA-cr89-8f7q-v4r4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cr89-8f7q-v4r4</link>
      <description>&lt;p&gt;Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cr89-8f7q-v4r4</guid>
    </item>
  </channel>
</rss>
