<?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-09T12:17:21.119384+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-341664</id>
    <title>EUVD-2026-341664</title>
    <updated>2026-10-09T12:17:21.177541+00:00</updated>
    <content>EUVD-2026-341664</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-341664"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-58368</id>
    <title>fkie_cve-2024-58368</title>
    <updated>2026-10-09T12:17:21.177581+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>SurrealDB versions before 1.1.0 fail to properly parse the ID, DB, and NS headers in HTTP REST API requests containing special characters. Unauthenticated attackers can send crafted HTTP requests with malformed header values to trigger an uncaught exception that crashes the server.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-58368"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-m24x-r6q3-2vp9</id>
    <title>GHSA-m24x-r6q3-2vp9 — Uncaught Exception processing HTTP Headers in SurrealDB</title>
    <updated>2026-10-09T12:17:21.177614+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: surrealdb</p>
<p>The `ID`, `DB` and `NS` headers accepted by the SurrealDB HTTP REST API would fail to parse when containing some special characters. This would cause a panic which would crash the SurrealDB server, leading to denial of service.</p>
<p>This issue only affects the SurrealDB binary; it does not affect the SurrealDB library.</p>
<p>### Impact</p>
<p>An unauthenticated client may issue an HTTP request to the SurrealDB HTTP REST API containing one of the affected headers with values containing special characters in order to crash the SurrealDB server. This does not require the SurrealDB server to be running with any specific capabilities other than exposing the affected interface.</p>
<p>### Patches</p>
<p>- Version 1.1.0 and later are not affected by this issue.</p>
<p>### Workarounds</p>
<p>Concerned users unable to update may want to limit untrusted access to the SurrealDB HTTP REST API unless such access is required by the application. To limit the impact of the denial of service, SurrealDB administrators may also want to ensure that the SurrealDB process is running so that it can be automatically re-started after a crash.</p>
<p>### Resources</p>
<p>- #2985 ([diff](https://github.com/surrealdb/surrealdb/pull/2985/files#diff-7ad06ddbb88d77138e5daf40a0dac5443d78947acd69a284a7c2bceb61f9c5f0L83-R119))</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-m24x-r6q3-2vp9"/>
  </entry>
</feed>
