<?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>Mon, 16 Nov 2026 20:42:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-394895</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-394895</link>
      <description>EUVD-2026-394895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-394895</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3583</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3583</link>
      <description>&lt;p&gt;When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately before a revocation request may be returned again to the client after revocation, until the relevant cache entry is cleared.&lt;/p&gt;
&lt;p&gt;The security consequence is that a revoked access token may be re-issued to the client during the cache lifetime. While the re-issued token is not treated as valid for API authorization, affected users may be unable to obtain a new valid access token until the cache is cleared, which can disrupt authentication flows.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately before a revocation request may be returned again to the client after revocation, until the relevant cache entry is cleared.&lt;/p&gt;
&lt;p&gt;The security consequence is that a revoked access token may be re-issued to the client during the cache lifetime. While the re-issued token is not treated as valid for API authorization, affected users may be unable to obtain a new valid access token until the cache is cleared, which can disrupt authentication flows.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3583</guid>
    </item>
    <item>
      <title>GHSA-r767-66jg-55q2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r767-66jg-55q2</link>
      <description>&lt;p&gt;When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately before a revocation request may be returned again to the client after revocation, until the relevant cache entry is cleared.&lt;/p&gt;
&lt;p&gt;The security consequence is that a revoked access token may be re-issued to the client during the cache lifetime. While the re-issued token is not treated as valid for API authorization, affected users may be unable to obtain a new valid access token until the cache is cleared, which can disrupt authentication flows.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately before a revocation request may be returned again to the client after revocation, until the relevant cache entry is cleared.&lt;/p&gt;
&lt;p&gt;The security consequence is that a revoked access token may be re-issued to the client during the cache lifetime. While the re-issued token is not treated as valid for API authorization, affected users may be unable to obtain a new valid access token until the cache is cleared, which can disrupt authentication flows.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r767-66jg-55q2</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4251 — WSO2 API Manager: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4251</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in WSO2 API Manager ausnutzen, um beliebigen Programmcode auszuführen, Informationen auszulesen, Dateien zu manipulieren, oder einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in WSO2 API Manager ausnutzen, um beliebigen Programmcode auszuführen, Informationen auszulesen, Dateien zu manipulieren, oder einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4251</guid>
    </item>
  </channel>
</rss>
