<?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>Sun, 04 Oct 2026 21:06:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-336471</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-336471</link>
      <description>EUVD-2026-336471</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-336471</guid>
    </item>
    <item>
      <title>fkie_cve-2026-62143</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-62143</link>
      <description>&lt;p&gt;A Server-Side Request Forgery (SSRF) protection bypass existed in the html_to_markdown expansion module of misp-modules.&lt;/p&gt;
&lt;p&gt;The module attempts to prevent requests to loopback, private, link-local, and other restricted IP address ranges. However, IP addresses were compared against the blocked ranges without first normalising IPv4-mapped IPv6 addresses.&lt;/p&gt;
&lt;p&gt;An authenticated attacker able to invoke the module could supply an IPv4-mapped IPv6 address, such as:&lt;/p&gt;
&lt;p&gt;http://[::ffff:127.0.0.1]/
http://[::ffff:169.254.169.254]/&lt;/p&gt;
&lt;p&gt;Alternatively, the attacker could use a hostname that resolves to an IPv4-mapped IPv6 address. These addresses were treated as IPv6 addresses and therefore did not match the corresponding blocked IPv4 ranges.&lt;/p&gt;
&lt;p&gt;Successful exploitation could cause the misp-modules server to connect to services available through its loopback interface, internal network, or link-local network. This could expose internal web services, administrative interfaces, or cloud instance metadata, with retrieved content potentially returned to the attacker as converted Markdown.&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed by normalising IPv4-mapped IPv6 addresses to their underlying IPv4 representation before applying the blocked-range checks. URLs without a valid hostname are now also rejected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A Server-Side Request Forgery (SSRF) protection bypass existed in the html_to_markdown expansion module of misp-modules.&lt;/p&gt;
&lt;p&gt;The module attempts to prevent requests to loopback, private, link-local, and other restricted IP address ranges. However, IP addresses were compared against the blocked ranges without first normalising IPv4-mapped IPv6 addresses.&lt;/p&gt;
&lt;p&gt;An authenticated attacker able to invoke the module could supply an IPv4-mapped IPv6 address, such as:&lt;/p&gt;
&lt;p&gt;http://[::ffff:127.0.0.1]/
http://[::ffff:169.254.169.254]/&lt;/p&gt;
&lt;p&gt;Alternatively, the attacker could use a hostname that resolves to an IPv4-mapped IPv6 address. These addresses were treated as IPv6 addresses and therefore did not match the corresponding blocked IPv4 ranges.&lt;/p&gt;
&lt;p&gt;Successful exploitation could cause the misp-modules server to connect to services available through its loopback interface, internal network, or link-local network. This could expose internal web services, administrative interfaces, or cloud instance metadata, with retrieved content potentially returned to the attacker as converted Markdown.&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed by normalising IPv4-mapped IPv6 addresses to their underlying IPv4 representation before applying the blocked-range checks. URLs without a valid hostname are now also rejected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-62143</guid>
    </item>
    <item>
      <title>GHSA-xv9c-v5pw-jxvf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xv9c-v5pw-jxvf</link>
      <description>&lt;p&gt;A Server-Side Request Forgery (SSRF) protection bypass existed in the html_to_markdown expansion module of misp-modules.&lt;/p&gt;
&lt;p&gt;The module attempts to prevent requests to loopback, private, link-local, and other restricted IP address ranges. However, IP addresses were compared against the blocked ranges without first normalising IPv4-mapped IPv6 addresses.&lt;/p&gt;
&lt;p&gt;An authenticated attacker able to invoke the module could supply an IPv4-mapped IPv6 address, such as:&lt;/p&gt;
&lt;p&gt;http://[::ffff:127.0.0.1]/
http://[::ffff:169.254.169.254]/&lt;/p&gt;
&lt;p&gt;Alternatively, the attacker could use a hostname that resolves to an IPv4-mapped IPv6 address. These addresses were treated as IPv6 addresses and therefore did not match the corresponding blocked IPv4 ranges.&lt;/p&gt;
&lt;p&gt;Successful exploitation could cause the misp-modules server to connect to services available through its loopback interface, internal network, or link-local network. This could expose internal web services, administrative interfaces, or cloud instance metadata, with retrieved content potentially returned to the attacker as converted Markdown.&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed by normalising IPv4-mapped IPv6 addresses to their underlying IPv4 representation before applying the blocked-range checks. URLs without a valid hostname are now also rejected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A Server-Side Request Forgery (SSRF) protection bypass existed in the html_to_markdown expansion module of misp-modules.&lt;/p&gt;
&lt;p&gt;The module attempts to prevent requests to loopback, private, link-local, and other restricted IP address ranges. However, IP addresses were compared against the blocked ranges without first normalising IPv4-mapped IPv6 addresses.&lt;/p&gt;
&lt;p&gt;An authenticated attacker able to invoke the module could supply an IPv4-mapped IPv6 address, such as:&lt;/p&gt;
&lt;p&gt;http://[::ffff:127.0.0.1]/
http://[::ffff:169.254.169.254]/&lt;/p&gt;
&lt;p&gt;Alternatively, the attacker could use a hostname that resolves to an IPv4-mapped IPv6 address. These addresses were treated as IPv6 addresses and therefore did not match the corresponding blocked IPv4 ranges.&lt;/p&gt;
&lt;p&gt;Successful exploitation could cause the misp-modules server to connect to services available through its loopback interface, internal network, or link-local network. This could expose internal web services, administrative interfaces, or cloud instance metadata, with retrieved content potentially returned to the attacker as converted Markdown.&lt;/p&gt;
&lt;p&gt;The vulnerability has been addressed by normalising IPv4-mapped IPv6 addresses to their underlying IPv4 representation before applying the blocked-range checks. URLs without a valid hostname are now also rejected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xv9c-v5pw-jxvf</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2294 — MISP: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2294</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in MISP ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in MISP ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2294</guid>
    </item>
  </channel>
</rss>
