How severe is CVE-2026-105849?

No CVSS score has been assigned to CVE-2026-105849 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-105849?

CVE-2026-105849 affects the following packages: payload (npm), payload (npm). Ecosystems affected: npm.

How do I fix CVE-2026-105849?

Update payload to 3.90.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-105849 is resolved across your whole dependency graph.

How do I detect CVE-2026-105849 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-105849 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-105849 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-105849 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-105849?

CVE-2026-105849 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-105849?

CVE-2026-105849 is classified as CWE-201 (CWE-201), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-105849 published, and has it been updated?

CVE-2026-105849 was published on October 6, 2026 and was last updated on October 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-105849 — payload

Fix: payloadcms/payload@880d2e9

CVE-2026-105849 is a CWE-201 vulnerability in payload. A fix is available for payload — see the affected versions and patch details below.

Payload: API key disclosure through ordinary document reads

Also known asGHSA-238x-w2j9-gwwr

Published

Oct 6, 2026

Updated

Oct 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-105849.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

114other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

payloadnpm

1.0Mdownloads / week

Description

Impact

Users with read access to other user documents could access their active API keys. An exposed key grants the target account’s permissions until rotated or disabled.

You are affected if:

An authentication collection enables useAPIKey.
Users have read access to other user documents containing active API keys.

Patches

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

Workarounds

Disable useAPIKey or restrict users to reading only their own authentication document. Rotate any API key that may have been exposed.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`payload`	≥ 3.0.0&&< 3.90.0	3.90.0`npm install payload@3.90.0`
📦npm	`payload`	≥ 4.0.0-canary.0&&< 4.0.0-canary.34	4.0.0-canary.34`npm install payload@4.0.0-canary.34`

Affected Products

1 product · 35 configurations

Application

payloadpayloadcms

≥ 3.0.0 && < 3.90.0

1 version

4.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update payload to 3.90.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-105849 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Users with read access to other user documents could access their active API keys. An exposed key grants the target account’s permissions until rotated or disabled. You are affected if: - An authentication collection enables `useAPIKey`. - Users have read access to other user documents containing active API keys. ### Patches Users should upgrade payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Disable `useAPIKey` or restrict users to reading only their own authentication document. Rotate any API key that may have been exposed.

O3 Security · Impact-Aware SCA

Is CVE-2026-105849 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works