<?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-03T23:37:42.952152+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/euvd-2026-8187</id>
    <title>EUVD-2026-8187</title>
    <updated>2026-10-03T23:37:43.012373+00:00</updated>
    <content>EUVD-2026-8187</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-8187"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-24609</id>
    <title>fkie_cve-2023-24609</title>
    <updated>2026-10-03T23:37:43.012424+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Matrix SSL 4.x through 4.6.0 and Rambus TLS Toolkit have a length-subtraction integer overflow for Client Hello Pre-Shared Key extension parsing in the TLS 1.3 server. An attacked device calculates an SHA-2 hash over at least 65 KB (in RAM). With a large number of crafted TLS messages, the CPU becomes heavily loaded. This occurs in tls13VerifyBinder and tls13TranscriptHashUpdate.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-24609"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-75jg-c8f9-x2rh</id>
    <title>GHSA-75jg-c8f9-x2rh</title>
    <updated>2026-10-03T23:37:43.012462+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Matrix SSL 4.x through 4.6.0 and Rambus TLS Toolkit have a length-subtraction integer overflow for Client Hello Pre-Shared Key extension parsing in the TLS 1.3 server. An attacked device calculates an SHA-2 hash over at least 65 KB (in RAM). With a large number of crafted TLS messages, the CPU becomes heavily loaded. This occurs in tls13VerifyBinder and tls13TranscriptHashUpdate.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-75jg-c8f9-x2rh"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-24609</id>
    <title>gsd-2023-24609</title>
    <updated>2026-10-03T23:37:43.012481+00:00</updated>
    <content>gsd-2023-24609</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-24609"/>
  </entry>
</feed>
