Disclosure summary
### 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.
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
GitHub Reviewed Security Advisories · GHSA-238x-w2j9-gwwr
Open original source · Updated Oct 06, 2026
Payload vulnerable to API key disclosure through ordinary document reads
Source severity: HIGH / 7.7
| Ecosystem | Package | Affected range | First patched |
|---|---|---|---|
| npm | payload | >= 3.0.0, < 3.90.0 | 3.90.0 |
| npm | payload | >= 4.0.0-canary.0, < 4.0.0-canary.34 | 4.0.0-canary.34 |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Reviewed advisory
PUBLISHED 2026-10-06T12:18:16-04:00
MODIFIED 2026-10-06T12:18:17-04:00
INGESTED 2026-10-08T12:05:11-04:00