CVE-2026-105865

Payload: Incomplete validation during the upload file lifecycle

Workarounds

Restrict upload update and deletion operations to trusted users and validate submitted filenames. These measures are temporary mitigations. Upgrading to a patched version is recommended.

Under certain conditions, an authenticated user with permission to modify uploads could cause unintended files to be removed during file cleanup. This may result in data loss or service disruption.

You are affected if:

• You use Payload upload collections with local file storage.
• Untrusted authenticated users can update or delete uploads.

Deployments that restrict upload management to trusted users are less exposed.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-105865 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.90.0, 4.0.0-canary.34); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Payload now validates uploaded filenames and ensures file cleanup remains within the configured upload directory.

Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

1. What is CVE-2026-105865? CVE-2026-105865 is a high-severity path traversal vulnerability in payload (npm), affecting versions < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-105865? CVE-2026-105865 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of payload are affected by CVE-2026-105865? payload (npm) versions < 3.90.0 is affected.
4. Is there a fix for CVE-2026-105865? Yes. CVE-2026-105865 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.
5. Is CVE-2026-105865 exploitable, and should I be worried? Whether CVE-2026-105865 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
6. What actually determines whether CVE-2026-105865 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.
7. How do I fix CVE-2026-105865?
   • Upgrade payload to 3.90.0 or later
   • Upgrade payload to 4.0.0-canary.34 or later

Other vulnerabilities in payload