CVE-2026-105862

validatedZero produced an exploit or a check.

GHSA-2pwp-2369-8fg3 ↗EUVD-2026-93508 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
payloadcms payload < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34
fixed in 3.90.0, 4.0.0-canary.34
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-839, permanent identifier
pkg:npm/payload
+1.4dTTV
41mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+33h33magent stopped
0
+12h
+24h
+36h

description

Payload versions before 3.90.0, and 4.0.0 canary releases before 4.0.0-canary.34, can retain unsafe SVG uploads in collections that permit SVG files. An attacker who can upload such a file may cause script execution when another user downloads and opens it. Exposure requires downloadable SVG uploads to be enabled.

mitigation

Upgrade payload to 3.90.0 or later, or to 4.0.0-canary.34 or later on the canary line. Until upgraded, block SVG uploads or force SVG responses to download as attachments with a restrictive content security policy.

fixed in 3.90.0, 4.0.0-canary.34

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.27%18th percentile
agent run time
41m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 16:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-06 16:37Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-105862

{
  "etk_id": "ETK-2026-839",
  "cve_id": "CVE-2026-105862",
  "display_id": "CVE-2026-105862",
  "ghsa_id": "GHSA-2pwp-2369-8fg3",
  "euvd_id": "EUVD-2026-93508",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored SVG cross-site scripting in payload uploads",
  "summary": "Payload versions before 3.90.0, and 4.0.0 canary releases before 4.0.0-canary.34, can retain unsafe SVG uploads in collections that permit SVG files. An attacker who can upload such a file may cause script execution when another user downloads and opens it. Exposure requires downloadable SVG uploads to be enabled.",
  "mitigation": "Upgrade payload to 3.90.0 or later, or to 4.0.0-canary.34 or later on the canary line. Until upgraded, block SVG uploads or force SVG responses to download as attachments with a restrictive content security policy.",
  "vendor": "payloadcms",
  "product": "payload",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 3.90.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "3.90.0"
      ],
      "package_name": "payload",
      "purl": "pkg:npm/payload"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0-canary.0, < 4.0.0-canary.34"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "4.0.0-canary.34"
      ],
      "package_name": "payload",
      "purl": "pkg:npm/payload"
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N",
  "epss_score": 0.0027,
  "epss_percentile": 0.1819,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 40.870299116666665,
  "t0_at": "2026-10-06T16:37:59.487000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-08T02:11:23.411629+00:00",
      "days": 1.3981935720949075,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T16:37:59.487000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-06T16:37:59.487000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T16:37:59.487000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105862"
    }
  }
}

published 2026-10-07 03:29Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.