Summary
Payload: Uploaded XML files could execute same-origin JavaScript
Workarounds
Disallow XML/XSL uploads.
Impact
Under certain local upload configurations, an uploaded XML file and stylesheet could execute JavaScript in the Payload origin when a logged-in user opens the file.
You are affected if:
- You accept XML uploads (accepted by default).
The application accepts file uploads without adequately restricting the file type or content. Typical impact: remote code execution if the uploaded file can be served and executed on the server.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Frequently Asked Questions
- What is CVE-2026-105868? CVE-2026-105868 is a high-severity unrestricted upload of dangerous file types vulnerability in payload (npm), affecting versions < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34. The application accepts file uploads without adequately restricting the file type or content.
- Which versions of payload are affected by CVE-2026-105868? payload (npm) versions < 3.90.0 is affected.
- Is there a fix for CVE-2026-105868? Yes. CVE-2026-105868 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.
- Is CVE-2026-105868 exploitable, and should I be worried? Whether CVE-2026-105868 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
- What actually determines whether CVE-2026-105868 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.
- How do I fix CVE-2026-105868?
- Upgrade
payloadto 3.90.0 or later - Upgrade
payloadto 4.0.0-canary.34 or later
- Upgrade