How severe is CVE-2026-105848?

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

Which packages are affected by CVE-2026-105848?

CVE-2026-105848 affects the following packages: @payloadcms/plugin-stripe (npm), @payloadcms/plugin-stripe (npm). Ecosystems affected: npm.

How do I fix CVE-2026-105848?

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

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

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

How do I mitigate CVE-2026-105848 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-105848 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-105848 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-105848?

CVE-2026-105848 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 15th 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-105848?

CVE-2026-105848 is classified as CWE-749 (CWE-749), 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-105848 published, and has it been updated?

CVE-2026-105848 was published on October 6, 2026 and was last updated on October 10, 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-105848 — @payloadcms/plugin-stripe

Fix: payloadcms/payload@2f94a42

CVE-2026-105848 is a CWE-749 vulnerability in @payloadcms/plugin-stripe. A fix is available for @payloadcms/plugin-stripe — see the affected versions and patch details below.

Payload: Insufficient Access Control in Stripe REST Proxy

Also known asGHSA-r9v2-gg2j-22q5

Published

Oct 6, 2026

Updated

Oct 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 13, 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-105848.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs15th percentile — riskier than 15% 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.

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

@payloadcms/plugin-stripenpm

15Kdownloads / week

Description

Impact

An authenticated user could perform unintended Stripe operations through the optional Stripe REST proxy.

You are affected if ALL of these are true:

Your application uses @payloadcms/plugin-stripe.
The optional Stripe REST proxy is enabled.
An authenticated user can reach the proxy.

Deployments that do not enable the Stripe REST proxy are not affected.

Patches

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

Workarounds

Upgrading to a patched version is recommended.

If you cannot upgrade immediately, disable the Stripe REST proxy. If it must remain enabled, restrict access to trusted users and only the required Stripe operations.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@payloadcms/plugin-stripe`	all versions	3.90.0`npm install @payloadcms/plugin-stripe@3.90.0`
📦npm	`@payloadcms/plugin-stripe`	≥ 4.0.0-canary.0&&< 4.0.0-canary.34	4.0.0-canary.34`npm install @payloadcms/plugin-stripe@4.0.0-canary.34`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @payloadcms/plugin-stripe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @payloadcms/plugin-stripe to 3.90.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-105848 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 An authenticated user could perform unintended Stripe operations through the optional Stripe REST proxy. **You are affected if ALL of these are true:** - Your application uses `@payloadcms/plugin-stripe`. - The optional Stripe REST proxy is enabled. - An authenticated user can reach the proxy. Deployments that do not enable the Stripe REST proxy are not affected. ## Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ## Workarounds Upgrading to a patched version is recommended. If you cannot upgrade immediately, disable the Stripe REST prox

O3 Security · Impact-Aware SCA

Is CVE-2026-105848 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works