Is CVE-2026-105862 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105862 being exploited in the wild.

How severe is CVE-2026-105862?

High severity, with a CVSS score of 8.7, published 6 October 2026.

Which products and versions are affected?

payload (npm) SEMVER:introduced=0,fixed=3.90.0; Payload CMS Payload before 3.90.0 and 4.0.0-canary before canary.34.

How is CVE-2026-105862 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-105862?

Check whether you run payload (npm) or Payload CMS Payload at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105862: Payload CMS stored XSS in SVG upload sanitization

CVE-2026-105862 · Severity: high · CVSS 8.7 · Published 2026-10-06

Payload CMS is a headless content management system that allows users to manage and deliver digital content. In versions before 3.90.0 and 4.0.0-canary.34, attackers could upload malicious SVG files that bypass content sanitization and execute arbitrary JavaScript when users download and open the SVG file. This could lead to account compromise or data theft from administrators who access the malicious files.

Technologies: payload (npm), Payload CMS Payload. Vendors: npm, Payload CMS.

Quick answers

Is CVE-2026-105862 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105862 being exploited in the wild.
How severe is CVE-2026-105862?: High severity, with a CVSS score of 8.7, published 6 October 2026.
Which products and versions are affected?: payload (npm) SEMVER:introduced=0,fixed=3.90.0; Payload CMS Payload before 3.90.0 and 4.0.0-canary before canary.34.
Is there a fix for CVE-2026-105862?: Yes. payload (npm): upgrade to 3.90.0 or later. Until then: Verify affected SVG and XML upload workflows and ensure custom upload clients send required metadata and returned headers. Set allowRestrictedFileTypes: true in the collections upload property if previous behavior is explicitly required.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-06"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105862 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-105862?: Check whether you run payload (npm) or Payload CMS Payload at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

payload (npm): upgrade to 3.90.0 or later
```
npm install payload@3.90.0
```

Verify affected SVG and XML upload workflows and ensure custom upload clients send required metadata and returned headers. Set allowRestrictedFileTypes: true in the collections upload property if previous behavior is explicitly required.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-06"}]

Technical details

The vulnerability is a stored cross-site scripting (XSS) flaw in SVG upload handling where malicious SVG content bypasses sanitization checks. An attacker with upload privileges to a collection that accepts SVG downloads can craft a malicious SVG file containing embedded JavaScript that executes in the context of a user's browser when the file is downloaded and opened. The fix validates upload identity and implements XML/SVG delivery restrictions via Content Security Policy headers.

Affected products

Payload CMS Payload before 3.90.0 and 4.0.0-canary before canary.34

Identifiers

CVE-2026-105862
GHSA-2pwp-2369-8fg3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.