<?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://db.gcve.eu</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>Thu, 08 Oct 2026 16:00:21 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-105862</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-105862</link>
      <description>&lt;p&gt;Payload is a free and open source headless content management system. In versions before 3.90.0 and canary versions before 4.0.0-canary.34, a collection that allows downloadable SVG uploads can store a malicious SVG that bypasses sanitization and executes attacker-controlled JavaScript when a user downloads and opens the SVG. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Payload is a free and open source headless content management system. In versions before 3.90.0 and canary versions before 4.0.0-canary.34, a collection that allows downloadable SVG uploads can store a malicious SVG that bypasses sanitization and executes attacker-controlled JavaScript when a user downloads and opens the SVG. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-105862</guid>
    </item>
    <item>
      <title>GHSA-2pwp-2369-8fg3 — Payload: Bypassed sanitization of user uploaded SVGs</title>
      <link>https://db.gcve.eu/vuln/ghsa-2pwp-2369-8fg3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: payload&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A malicious SVG file upload could bypass sanitization, be stored, and execute attacker-controlled JavaScript (XSS) after a user downloads it and opens it.&lt;/p&gt;
&lt;p&gt;**You are affected if:**&lt;/p&gt;
&lt;p&gt;- You have a collection configured to upload and allow SVG files which can then be downloaded by users.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The fix validates SVG content on every upload path and hardens SVG/XML delivery so stored SVGs cannot frame attacker content.&lt;/p&gt;
&lt;p&gt;Users should upgrade Payload packages to `&amp;gt;= 3.90.0` or `&amp;gt;= 4.0.0-canary.34`.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP. These mitigations reduce exposure but do not replace upgrading when the patched release is available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: payload&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A malicious SVG file upload could bypass sanitization, be stored, and execute attacker-controlled JavaScript (XSS) after a user downloads it and opens it.&lt;/p&gt;
&lt;p&gt;**You are affected if:**&lt;/p&gt;
&lt;p&gt;- You have a collection configured to upload and allow SVG files which can then be downloaded by users.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The fix validates SVG content on every upload path and hardens SVG/XML delivery so stored SVGs cannot frame attacker content.&lt;/p&gt;
&lt;p&gt;Users should upgrade Payload packages to `&amp;gt;= 3.90.0` or `&amp;gt;= 4.0.0-canary.34`.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP. These mitigations reduce exposure but do not replace upgrading when the patched release is available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2pwp-2369-8fg3</guid>
    </item>
  </channel>
</rss>
