What is CVE-2026-105855?

CVE-2026-105855 is a high-severity security vulnerability in payload (npm), affecting versions < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34.

Which versions of payload are affected by CVE-2026-105855?

payload (npm) versions < 3.90.0 is affected.

Is there a fix for CVE-2026-105855?

Yes. CVE-2026-105855 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.

Is CVE-2026-105855 exploitable, and should I be worried?

Whether CVE-2026-105855 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.

What actually determines whether CVE-2026-105855 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-105855?

Upgrade: payload to 3.90.0 or later, payload to 4.0.0-canary.34 or later.

CVE-2026-105855 in payload

Q: Which versions of payload are affected by CVE-2026-105855?

payload (npm) versions < 3.90.0 is affected.

Q: Is there a fix for CVE-2026-105855?

Yes. CVE-2026-105855 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.

Q: Is CVE-2026-105855 exploitable, and should I be worried?

Whether CVE-2026-105855 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.

Q: What actually determines whether CVE-2026-105855 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.

Q: How do I fix CVE-2026-105855?

Upgrade: payload to 3.90.0 or later, payload to 4.0.0-canary.34 or later.

Summary

Payload didn't enforce field-level password update restrictions

Impact

When an auth collection defined a field-level access.update restriction on the password field, the restriction was not enforced on the server correctly.

Affected versions

payload (< 3.90.0) payload (>= 4.0.0-canary.0, < 4.0.0-canary.34)

Security releases

payload → 3.90.0 (npm) payload → 4.0.0-canary.34 (npm)

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 environment New 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-105855? CVE-2026-105855 is a high-severity security vulnerability in payload (npm), affecting versions < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34.
Which versions of payload are affected by CVE-2026-105855? payload (npm) versions < 3.90.0 is affected.
Is there a fix for CVE-2026-105855? Yes. CVE-2026-105855 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.
Is CVE-2026-105855 exploitable, and should I be worried? Whether CVE-2026-105855 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-105855 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-105855?
- Upgrade payload to 3.90.0 or later
- Upgrade payload to 4.0.0-canary.34 or later

Other vulnerabilities in payload

CVE-IDSeverityPackage summary

CVE-2026-105858Highpayload: Payload: Remote Code Execution through first-register CVE-2026-105861Highpayload: Payload external upload trust validation issue CVE-2026-105862Highpayload: Payload: Bypassed sanitization of user uploaded SVGs CVE-2026-105865Highpayload: Payload: Incomplete validation during the upload file lifecycle CVE-2026-105866Mediumpayload: Payload: Unauthenticated account-lockout denial of service