<?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, 05 Oct 2026 20:49:58 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0523 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0523</link>
      <description>certfr-2026-avi-0523</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0523</guid>
    </item>
    <item>
      <title>EUVD-2026-160118</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-160118</link>
      <description>EUVD-2026-160118</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-160118</guid>
    </item>
    <item>
      <title>fkie_cve-2024-31033</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-31033</link>
      <description>&lt;p&gt;JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class. NOTE: the vendor disputes this because the &amp;#34;ignores&amp;#34; behavior cannot occur (in any version) unless there is a user error in how JJWT is used, and because the version that was actually tested must have been more than six years out of date.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class. NOTE: the vendor disputes this because the &amp;#34;ignores&amp;#34; behavior cannot occur (in any version) unless there is a user error in how JJWT is used, and because the version that was actually tested must have been more than six years out of date.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-31033</guid>
    </item>
    <item>
      <title>Withdrawn: GHSA-r65j-6h5f-4f92 — Withdrawn: JJWT improperly generates signing keys</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r65j-6h5f-4f92</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.jsonwebtoken:jjwt-impl&lt;/p&gt;
&lt;p&gt;## Withdrawn Advisory&lt;/p&gt;
&lt;p&gt;This advisory has been withdrawn because it has been found to be disputed. Please see the issue [here](https://github.com/jwtk/jjwt/issues/930#issuecomment-2032699358) for more information.&lt;/p&gt;
&lt;p&gt;## Original Description&lt;/p&gt;
&lt;p&gt;JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.jsonwebtoken:jjwt-impl&lt;/p&gt;
&lt;p&gt;## Withdrawn Advisory&lt;/p&gt;
&lt;p&gt;This advisory has been withdrawn because it has been found to be disputed. Please see the issue [here](https://github.com/jwtk/jjwt/issues/930#issuecomment-2032699358) for more information.&lt;/p&gt;
&lt;p&gt;## Original Description&lt;/p&gt;
&lt;p&gt;JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r65j-6h5f-4f92</guid>
    </item>
    <item>
      <title>gsd-2024-31033</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-31033</link>
      <description>gsd-2024-31033</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-31033</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1273 — IBM Business Automation Workflow: Schwachstelle ermöglicht nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1273</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM Business Automation Workflow ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM Business Automation Workflow ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1273</guid>
    </item>
  </channel>
</rss>
