Cross-Site Scripting (XSS) in payload (CVE-2026-105862)
Summary
Cross-site scripting in payload (CVE-2026-105862). Confidential information can be exposed externally. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105862 has been found in payload.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade payload to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "payload CVE-2026-105862" on the vendor's site.
CVE-2026-105862 (payload) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Patched: 4.0.0-canary.34 — apply immediately
Workaround: Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in payload.
Check the vendor advisory for the affected versions of payload.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 4.0.0-canary.34.
Workaround: Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'payload' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'payload' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
payloadを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP.パッチが適用されるまでの応急処置として、Disallow SVG uploads, or serve uploaded SVGs as downloads with Content-Disposition: attachment and a strict CSP. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade payload to 4.0.0-canary.34ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com