<?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>Tue, 06 Oct 2026 20:59:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233468</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233468</link>
      <description>EUVD-2026-233468</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233468</guid>
    </item>
    <item>
      <title>fkie_cve-2022-39351</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-39351</link>
      <description>&lt;p&gt;Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.6.0, performing an API request using a valid API key with insufficient permissions causes the API key to be written to Dependency-Track&amp;#39;s audit log in clear text. Actors with access to the audit log can exploit this flaw to gain access to valid API keys. The issue has been fixed in Dependency-Track 4.6.0. Instead of logging the entire API key, only the last 4 characters of the key will be logged. It is strongly recommended to check historic logs for occurrences of this behavior, and re-generating API keys in case of leakage.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.6.0, performing an API request using a valid API key with insufficient permissions causes the API key to be written to Dependency-Track&amp;#39;s audit log in clear text. Actors with access to the audit log can exploit this flaw to gain access to valid API keys. The issue has been fixed in Dependency-Track 4.6.0. Instead of logging the entire API key, only the last 4 characters of the key will be logged. It is strongly recommended to check historic logs for occurrences of this behavior, and re-generating API keys in case of leakage.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-39351</guid>
    </item>
    <item>
      <title>gsd-2022-39351</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-39351</link>
      <description>gsd-2022-39351</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-39351</guid>
    </item>
  </channel>
</rss>
