<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T22:28:58.358600+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2021-avi-395</id>
    <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>
    <updated>2026-10-05T22:28:58.362662+00:00</updated>
    <content>certfr-2021-avi-395</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2021-avi-395"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2021-13225</id>
    <title>cnvd-2021-13225</title>
    <updated>2026-10-05T22:28:58.362698+00:00</updated>
    <content>cnvd-2021-13225</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2021-13225"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-215956</id>
    <title>EUVD-2026-215956</title>
    <updated>2026-10-05T22:28:58.362713+00:00</updated>
    <content>EUVD-2026-215956</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-215956"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-26296</id>
    <title>fkie_cve-2021-26296</title>
    <updated>2026-10-05T22:28:58.362724+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-26296"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-gq67-pp9w-43gp</id>
    <title>GHSA-gq67-pp9w-43gp — Cryptographically weak CSRF tokens in Apache MyFaces</title>
    <updated>2026-10-05T22:28:58.362751+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.apache.myfaces.core:myfaces-core-module</p>
<p>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.</p>
<p>Mitigation:
Existing web.xml configuration parameters can be used to direct
MyFaces to use SecureRandom for CSRF token generation:</p>
<p>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</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-gq67-pp9w-43gp"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-26296</id>
    <title>gsd-2021-26296</title>
    <updated>2026-10-05T22:28:58.362781+00:00</updated>
    <content>gsd-2021-26296</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-26296"/>
  </entry>
</feed>
