CVE-2026-105859 payloadcms CVE debrief

Who should care

Defenders and developers using Payload packages should assess exposure and upgrade to patched versions. This includes operators, platforms, vulnerability-management, and security teams that rely on Payload packages for their systems and applications. They need to verify access control enforcement in the patched version and assess exposure by checking if `orderable: true` is configured with any collection or join field. Upgrading to patched versions and re审

Why it matters

CVE-2026-105859 allows unauthorized updates to collection documents. Defenders and developers using Payload packages should assess exposure and upgrade to patched versions.

• Verify access control enforcement in the patched version
• Assess exposure by checking if `orderable: true` is configured with any collection or join field
• Upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34

Technical summary

An attacker can submit a request to a specific endpoint that permits collection documents to be updated regardless of access control and field level access control. You are affected if you are configuring `orderable: true` with any collection or join field. The patched version properly enforces access control. Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. The vulnerability allows unauthorized updates to collection documents, impacting defenders and developers using Payload packages. They should assess exposure and upgrade to patched versions.

Defensive priority

Upgrade to patched version, assess exposure

Recommended defensive actions

• Upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34
• Assess exposure by checking if `orderable: true` is configured with any collection or join field
• Verify access control enforcement in the patched version
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability. The source item mentions that an attacker can submit a request to a specific endpoint that permits collection documents to be updated regardless of access control and field level access control.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.