CVE-2026-105862

Payload: Bypassed sanitization of user uploaded SVGs

Workarounds

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.

A malicious SVG file upload could bypass sanitization, be stored, and execute attacker-controlled JavaScript (XSS) after a user downloads it and opens it.

You are affected if:

• You have a collection configured to upload and allow SVG files which can then be downloaded by users.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-105862 has a CVSS score of 8.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.90.0, 4.0.0-canary.34); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The fix validates SVG content on every upload path and hardens SVG/XML delivery so stored SVGs cannot frame attacker content.

Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

1. What is CVE-2026-105862? CVE-2026-105862 is a high-severity cross-site scripting (XSS) vulnerability in payload (npm), affecting versions < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-105862? CVE-2026-105862 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of payload are affected by CVE-2026-105862? payload (npm) versions < 3.90.0 is affected.
4. Is there a fix for CVE-2026-105862? Yes. CVE-2026-105862 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.
5. Is CVE-2026-105862 exploitable, and should I be worried? Whether CVE-2026-105862 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-105862 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-105862?
   • Upgrade payload to 3.90.0 or later
   • Upgrade payload to 4.0.0-canary.34 or later

Other vulnerabilities in payload