CVE.org (no NVD analysis yet)· CNA GitHub_M

CVE-2026-105867: Payload: Client uploads could overwrite S3 objects

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: @payloadcms/storage-s3 (npm) 4.0.0-canary.34, 3.90.0.

Low priority for now. Upgrade to @payloadcms/storage-s3 (npm) 4.0.0-canary.34, 3.90.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Payload is a free and open source headless content management system. In @payloadcms/storage-s3 versions before 3.90.0 and canary versions before 4.0.0-canary.34, an authenticated user can overwrite an existing S3 object belonging to another upload collection when client uploads are enabled for multiple collections sharing a bucket and useCompositePrefixes is false or unset. This bypasses the target collection's access controls and prior file validation. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

HighCVSS 7.1 · v4.0—No exploit Fix available

Broken access control (IDOR)

Published: Oct 6, 2026
Updated: Oct 15, 2026
EPSS: 0.2% · 12th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.1; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
payloadcms	payload	cpe:2.3:a:payloadcms:payload

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

payloadcms payloadbefore 3.90.0
payloadcms payload4.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

@payloadcms storage-s3
- < 3.90.0, >= 4.0.0-canary.0, < 4.0.0-canary.34affected
payloadcms payload
- < 3.90.0, >= 4.0.0-canary.0, < 4.0.0-canary.34affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
npm	@payloadcms/storage-s3	from 4.0.0-canary.0 · before 4.0.0-canary.34	4.0.0-canary.34
npm	@payloadcms/storage-s3	before 3.90.0	3.90.0

Same product

payloadcms: all records

Other highest-scoring records for the same primary product.

CVE-2026-105857Payload: RCE in Payload Form Builder
40Plan
CVE-2022-27952An arbitrary file upload vulnerability in the file upload module of PayloadCMS v0.15.0 allows attackers to execute arbitrary code via a craf
40Plan
CVE-2026-105859Payload: Unauthorized update to collection documents
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-105865Oct 6, 2026 · Payload: Incomplete validation during the upload file lifecycle
32Monitor
← EarlierCVE-2026-105866Oct 6, 2026 · Payload: Unauthenticated account-lockout denial of service
27Monitor
Later →CVE-2026-105868Oct 6, 2026 · Payload: Uploaded XML files could execute same-origin JavaScript
34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
npm:@payloadcms/storage-s3	3.90.0	Package registry (OSV)
npm:@payloadcms/storage-s3	4.0.0-canary.34	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 6, 2026
Fix recordedOct 8, 2026+1 d
TodayOct 26, 2026+20 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

payloadcms/payloadcommit 2df8238

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1058590 days apartPayload: Unauthorized update to collection documents
39Monitor
CVE-2026-1061000 days apartPayload: Field-level write access bypass in Payload on MongoDB
28Monitor
CVE-2026-25574242 days apartPayload Affected by Cross-Collection IDOR in payload-preferences Access Control (Multi-Auth Environments)
21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Oct 8, 2026, 3:30 AM UTC
SSVC exploitation— → noneOct 6, 2026, 7:07 PM UTC
Exploit maturity— → noneOct 6, 2026, 6:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/payloadcms/payload/commit/2df8238fbf17edfce335c399b90bf524ba9906a2

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records