CVE-2026-105844: Payload: Prototype pollution in Payload Import Export plugin

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Payload is a free and open source headless content management system. In versions from 3.0.0 before 3.88.0 and canary versions before 4.0.0-canary.27, an unauthenticated user can submit prototype-sensitive field paths when @payloadcms/plugin-import-export is enabled, causing unintended application behavior that can lead to remote code execution. This issue is fixed in versions 3.88.0 and 4.0.0-canary.27.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-06).

Weakness: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes (‘Prototype Pollution’)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 4 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 9 references on Exploit Observer

Live scores

EPSS
0.007
low predicted chance of attack
VEDAS
0.982
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
payloadcms payloadversion >= 3.0.0, < 3.88.0
version >= 4.0.0-canary.0, < 4.0.0-canary.27
Not stated
@payloadcms plugin-import-exportversion >= 3.0.0, < 3.88.0
version >= 4.0.0-canary.0, < 4.0.0-canary.27
Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-105844 Payload CMS - Prototype Pollution Access Control Bypass. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-105844 Payload CMS - Prototype Pollution Access Control Bypass"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"export-preview"; nocase; fast_pattern; http.request_body; content:"__proto__"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-105844; reference:url,https://www.exploit.observer/?keyword=CVE-2026-105844&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=payloadcms&match=exact; sid:1104200; rev:1;)

CVE-2026-105844.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust