NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Cross-Site Request Forgery (CSRF) in Auth0GHSA-wv26-rj8c-4r33

HIGH

GHSA-wv26-rj8c-4r33 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in auth0-js. A fix is available for auth0-js — see the affected versions and patch details below.

Also known asCVE-2018-6874
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.43%0.85%1.28%0.2%0.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg 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.

416other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
auth0-jsnpm
374Kdownloads / week

Description

CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmauth0-jsall versions9.0.0npm install auth0-js@9.0.0

Affected Products

1 product · 1 configurations
Application
auth0.jsauth0
≤ 8.12.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update auth0-js to 9.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wv26-rj8c-4r33 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.
O3 Security · Impact-Aware SCA

Is GHSA-wv26-rj8c-4r33 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Cross-Site Request Forgery (CSRF) in Auth0 (High 8.8)