<?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 22:28:48 +0000</lastBuildDate>
    <item>
      <title>certfr-2021-avi-395 — De multiples vulnérabilités ont été découvertes dans IBM Spectrum
Control. Certaines d'entre elles permettent à un atta…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2021-avi-395</link>
      <description>certfr-2021-avi-395</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2021-avi-395</guid>
    </item>
    <item>
      <title>cnvd-2021-13225</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-13225</link>
      <description>cnvd-2021-13225</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-13225</guid>
    </item>
    <item>
      <title>EUVD-2026-215956</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-215956</link>
      <description>EUVD-2026-215956</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-215956</guid>
    </item>
    <item>
      <title>fkie_cve-2021-26296</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-26296</link>
      <description>&lt;p&gt;In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-26296</guid>
    </item>
    <item>
      <title>GHSA-gq67-pp9w-43gp — Cryptographically weak CSRF tokens in Apache MyFaces</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gq67-pp9w-43gp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.myfaces.core:myfaces-core-module&lt;/p&gt;
&lt;p&gt;In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.&lt;/p&gt;
&lt;p&gt;Mitigation:
Existing web.xml configuration parameters can be used to direct
MyFaces to use SecureRandom for CSRF token generation:&lt;/p&gt;
&lt;p&gt;org.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom
org.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom
org.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.myfaces.core:myfaces-core-module&lt;/p&gt;
&lt;p&gt;In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.&lt;/p&gt;
&lt;p&gt;Mitigation:
Existing web.xml configuration parameters can be used to direct
MyFaces to use SecureRandom for CSRF token generation:&lt;/p&gt;
&lt;p&gt;org.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom
org.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom
org.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gq67-pp9w-43gp</guid>
    </item>
    <item>
      <title>gsd-2021-26296</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-26296</link>
      <description>gsd-2021-26296</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-26296</guid>
    </item>
  </channel>
</rss>
