<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 15:59:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90957 — MISP: Stored XSS via Inline-Served SVG Organisation Logos and Report Pictures</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90957</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MISP&lt;/p&gt;
&lt;p&gt;Affected versions of MISP serve uploaded SVG images inline without a restrictive browser sandbox.&lt;/p&gt;
&lt;p&gt;The commit explains that SVG files are XML documents rather than passive bitmap images. While scripts inside SVG do not execute when the SVG is rendered through a normal &amp;lt;img&amp;gt;, they can execute when the SVG is navigated to directly or embedded as a document. In that case, malicious &amp;lt;script&amp;gt; elements, event handlers, or javascript: URLs execute on the MISP origin with the viewer’s session.&lt;/p&gt;
&lt;p&gt;The affected use cases include:&lt;/p&gt;
&lt;p&gt;- organisation SVG logos;
 - event-report SVG pictures.&lt;/p&gt;
&lt;p&gt;Importantly, the vulnerable behavior is on the serve path, not merely the upload path: the patch notes that a malicious SVG uploaded while SVG support was enabled could remain dangerous even after uploads were later disabled.&lt;/p&gt;
&lt;p&gt;Version affected: ≤2.5.45&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MISP&lt;/p&gt;
&lt;p&gt;Affected versions of MISP serve uploaded SVG images inline without a restrictive browser sandbox.&lt;/p&gt;
&lt;p&gt;The commit explains that SVG files are XML documents rather than passive bitmap images. While scripts inside SVG do not execute when the SVG is rendered through a normal &amp;lt;img&amp;gt;, they can execute when the SVG is navigated to directly or embedded as a document. In that case, malicious &amp;lt;script&amp;gt; elements, event handlers, or javascript: URLs execute on the MISP origin with the viewer’s session.&lt;/p&gt;
&lt;p&gt;The affected use cases include:&lt;/p&gt;
&lt;p&gt;- organisation SVG logos;
 - event-report SVG pictures.&lt;/p&gt;
&lt;p&gt;Importantly, the vulnerable behavior is on the serve path, not merely the upload path: the patch notes that a malicious SVG uploaded while SVG support was enabled could remain dangerous even after uploads were later disabled.&lt;/p&gt;
&lt;p&gt;Version affected: ≤2.5.45&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90957</guid>
    </item>
  </channel>
</rss>
