NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-105849: Payload vulnerable to API key disclosure through ordinary document reads

highCVSS 4.0 7.7GHSA-238x-w2j9-gwwr

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.

Published Oct 6, 2026

Affected packages

payload

Ecosystem
npm
Affected
>= 3.0.0, < 3.90.0
Fixed in
3.90.0
Check
npm ls payload

payload

Ecosystem
npm
Affected
>= 4.0.0-canary.0, < 4.0.0-canary.34
Fixed in
4.0.0-canary.34
Check
npm ls payload

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to Zerotistic.

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

More npm vulnerabilities

All npm entries