<?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>Fri, 02 Oct 2026 19:39:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266438</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266438</link>
      <description>EUVD-2026-266438</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266438</guid>
    </item>
    <item>
      <title>fkie_cve-2025-24976</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-24976</link>
      <description>&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Systems running registry versions 3.0.0-beta.1 through 3.0.0-rc.2 with token authentication enabled may be vulnerable to an issue in which token authentication allows an attacker to inject an untrusted signing key in a JSON web token (JWT). The issue lies in how the JSON web key (JWK) verification is performed. When a JWT contains a JWK header without a certificate chain, the code only checks if the KeyID (`kid`) matches one of the trusted keys, but doesn&amp;#39;t verify that the actual key material matches. A fix for the issue is available at commit 5ea9aa028db65ca5665f6af2c20ecf9dc34e5fcd and expected to be a part of version 3.0.0-rc.3. There is no way to work around this issue without patching if the system requires token authentication.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Systems running registry versions 3.0.0-beta.1 through 3.0.0-rc.2 with token authentication enabled may be vulnerable to an issue in which token authentication allows an attacker to inject an untrusted signing key in a JSON web token (JWT). The issue lies in how the JSON web key (JWK) verification is performed. When a JWT contains a JWK header without a certificate chain, the code only checks if the KeyID (`kid`) matches one of the trusted keys, but doesn&amp;#39;t verify that the actual key material matches. A fix for the issue is available at commit 5ea9aa028db65ca5665f6af2c20ecf9dc34e5fcd and expected to be a part of version 3.0.0-rc.3. There is no way to work around this issue without patching if the system requires token authentication.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-24976</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:14889-1 — govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14889-1</link>
      <description>&lt;p&gt;govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:14889-1</guid>
    </item>
    <item>
      <title>RHSA-2025:2445 — Red Hat Security Advisory: OpenShift Container Platform 4.17.20 bug fix and security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:2445</link>
      <description>&lt;p&gt;buildah: Buildah allows arbitrary directory mount kernel: HID: core: zero-initialize the report buffer distribution: Distribution&amp;#39;s token authentication allows attacker to inject an untrusted signing key in a JWT&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;buildah: Buildah allows arbitrary directory mount kernel: HID: core: zero-initialize the report buffer distribution: Distribution&amp;#39;s token authentication allows attacker to inject an untrusted signing key in a JWT&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:2445</guid>
    </item>
  </channel>
</rss>
