<?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>Sat, 03 Oct 2026 18:57:28 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-369981</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-369981</link>
      <description>EUVD-2026-369981</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-369981</guid>
    </item>
    <item>
      <title>fkie_cve-2026-76820</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-76820</link>
      <description>&lt;p&gt;OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260701.0, the synchronizerFetch GraphQL query called fetchRemoteStreams after checking only that a remote stream URL used HTTP or HTTPS. The backend did not apply the ingestion deny list or reject private, loopback, and link-local destinations, allowing an authenticated account with the INGESTION capability to make OpenCTI request internal services and cloud metadata endpoints. Returned connection errors could distinguish open HTTP ports, open non-HTTP ports, and closed ports, enabling internal network scanning, while compatible endpoint responses could disclose internal data. This issue is fixed in version 7.260701.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260701.0, the synchronizerFetch GraphQL query called fetchRemoteStreams after checking only that a remote stream URL used HTTP or HTTPS. The backend did not apply the ingestion deny list or reject private, loopback, and link-local destinations, allowing an authenticated account with the INGESTION capability to make OpenCTI request internal services and cloud metadata endpoints. Returned connection errors could distinguish open HTTP ports, open non-HTTP ports, and closed ports, enabling internal network scanning, while compatible endpoint responses could disclose internal data. This issue is fixed in version 7.260701.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-76820</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3210 — OpenCTI: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3210</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenCTI ausnutzen, um beliebigen Code beziehungsweise Befehle im Kontext des OpenCTI-Servers auszuführen, interne Netzwerkdienste und Cloud-Metadaten über SSRF aufzurufen oder auszuspähen sowie fremde Draft Workspaces einschließlich zugehöriger Dateien und Daten unberechtigt zu löschen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenCTI ausnutzen, um beliebigen Code beziehungsweise Befehle im Kontext des OpenCTI-Servers auszuführen, interne Netzwerkdienste und Cloud-Metadaten über SSRF aufzurufen oder auszuspähen sowie fremde Draft Workspaces einschließlich zugehöriger Dateien und Daten unberechtigt zu löschen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3210</guid>
    </item>
  </channel>
</rss>
