GHSA-2pwp-2369-8fg3: XSS

Q: Which deployments are exposed to this issue?

Deployments are affected if they have a collection configured to accept SVG uploads and users can download those uploaded SVG files. The issue applies to the Payload npm package.

Q: What must an attacker do to trigger the vulnerability?

An attacker needs permission to upload a malicious SVG to an SVG-enabled collection. The stored payload executes attacker-controlled JavaScript when another user downloads and opens the file.

Q: What versions contain the fix?

Upgrade Payload packages to version 3.90.0 or later, or to 4.0.0-canary.34 or later. The fix validates SVG content on every upload path and hardens SVG/XML delivery.

Q: What can be done before upgrading?

Disallow SVG uploads, or serve uploaded SVGs as downloads using Content-Disposition: attachment and a strict Content Security Policy. These measures reduce exposure but are not a replacement for upgrading.

Published Oct 7, 2026

Updated

Impact

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.

Patches

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.

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.

Affected Software

2 affected componentsFixes available

npm/payload>=4.0.0-canary.0<4.0.0-canary.34

4.0.0-canary.34

npm/payload<3.90.0

3.90.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade npm/payload to a version that resolves this vulnerability.
Fixed in 4.0.0-canary.34
Upgrade
Upgrade npm/payload to a version that resolves this vulnerability.
Fixed in 3.90.0
Upgrade
Upgrade Payload packages to a version that resolves this vulnerability.
Fixed in 3.90.0
Upgrade
Upgrade Payload packages to a version that resolves this vulnerability.
Fixed in 4.0.0-canary.34
Configuration
Disallow SVG file uploads for collections that allow users to download uploaded files.
Collection file uploads SVG uploads = disabled
Configuration
Serve uploaded SVG files with Content-Disposition: attachment and a strict Content Security Policy.
Uploaded SVG delivery Content-Disposition and CSP = attachment; strict CSP

Event History

Oct 7, 2026

Advisory Published

via GitHub·08:29 PM

Data Sourced

via GitHub·08:29 PM

DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

Which deployments are exposed to this issue?

Deployments are affected if they have a collection configured to accept SVG uploads and users can download those uploaded SVG files. The issue applies to the Payload npm package.

What must an attacker do to trigger the vulnerability?

An attacker needs permission to upload a malicious SVG to an SVG-enabled collection. The stored payload executes attacker-controlled JavaScript when another user downloads and opens the file.

What versions contain the fix?

Upgrade Payload packages to version 3.90.0 or later, or to 4.0.0-canary.34 or later. The fix validates SVG content on every upload path and hardens SVG/XML delivery.

What can be done before upgrading?

Disallow SVG uploads, or serve uploaded SVGs as downloads using Content-Disposition: attachment and a strict Content Security Policy. These measures reduce exposure but are not a replacement for upgrading.

GHSA-2pwp-2369-8fg3: XSS

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed to this issue?

What must an attacker do to trigger the vulnerability?

What versions contain the fix?

What can be done before upgrading?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to this issue?

What must an attacker do to trigger the vulnerability?

What versions contain the fix?

What can be done before upgrading?