CVE-2026-105848: Payload: Insufficient Access Control in Stripe REST Proxy
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.
Published Oct 6, 2026
Affected packages
@payloadcms/plugin-stripe
- Ecosystem
- npm
- Affected
- < 3.90.0
- Fixed in
- 3.90.0
- Check
npm ls @payloadcms/plugin-stripe
@payloadcms/plugin-stripe
- Ecosystem
- npm
- Affected
- >= 4.0.0-canary.0, < 4.0.0-canary.34
- Fixed in
- 4.0.0-canary.34
- Check
npm ls @payloadcms/plugin-stripe
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
