
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 3.0.0, < 3.90.0
Patched in 3.90.0
Vulnerable: >= 4.0.0-canary.0, < 4.0.0-canary.34
Patched in 4.0.0-canary.34
Details
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:
useAPIKey.Users should upgrade payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Disable useAPIKey or restrict users to reading only their own authentication document. Rotate any API key that may have been exposed.
EPSS, exploit probability
Low0.30%
estimated chance of real-world exploitation in the next 30 days, higher than 23.3% of every CVE FIRST.org scores
Refreshed 11/20/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
More npm advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.