How severe is GHSA-pg53-56cg-4m8q?

No CVSS score has been assigned to GHSA-pg53-56cg-4m8q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pg53-56cg-4m8q?

GHSA-pg53-56cg-4m8q affects the following packages: next-auth (npm). Ecosystems affected: npm.

How do I fix GHSA-pg53-56cg-4m8q?

Update next-auth to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pg53-56cg-4m8q is resolved across your whole dependency graph.

How do I detect GHSA-pg53-56cg-4m8q in my npm dependencies?

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

How do I mitigate GHSA-pg53-56cg-4m8q if there is no patch (or I can't update yet)?

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.

Is GHSA-pg53-56cg-4m8q actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-pg53-56cg-4m8q, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-pg53-56cg-4m8q?

GHSA-pg53-56cg-4m8q has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 76th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pg53-56cg-4m8q?

GHSA-pg53-56cg-4m8q is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pg53-56cg-4m8q published, and has it been updated?

GHSA-pg53-56cg-4m8q was published on February 11, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Token verification bug in next-authGHSA-pg53-56cg-4m8q

GHSA-pg53-56cg-4m8q is a CWE-290 vulnerability in next-auth. 1 public exploit reference exists, so weaponization risk is real. A fix is available for next-auth — see the affected versions and patch details below.

Also known asCVE-2021-21310

Published

Feb 11, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

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

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.

599other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

next-authnpm

6.8Mdownloads / week

Description

Impact

Implementations using the Prisma database adapter with the Email provider are impacted.

Implementations using the Prisma database adapter that are not using the Email provider are not impacted. Implementations using the default database adapter (TypeORM) with the Email provider are not impacted. Implementations not using a database are not impacted.

Patches

This issue is fixed in 3.3.0 and newer versions.

Workarounds

Those not able to upgrade can alternatively disable the Email provider as a workaround.

Description

The Prisma database adapter was checking the verification token but not the identifier (the email address associated with the token). This made it possible to use a valid token assigned to one user, to sign in as another user when using the Prima adapter in conjunction with the Email provider. The defect is specific to the community-supported Prisma database adapter in versions <3.3.0 and is not present in the default database adapter (TypeORM).

Note: The current community-supported adapter was not developed by Prisma.

The defect was a problem in the implementation of verification function the adapter and is not directly related to Prisma.

The flaw may exist in other third party database adapters that do not check both the identifier and token values.

The design of the database adapter API may be revised in future to help reduce the likelyhood of similar defects.

Timeline

On Monday (2021-02-08) we were notified via responsible disclosure by Alessandro Angelino (@AlessandroA) of a flaw in the implementation of the Prisma database adapter included with NextAuth.js. A detailed write up and proof of concept were provided.

The following day (2021-02-09) we published a fix in v3.3.0 and confirmed through internal testing, and with Alessandro, that the issue was resolved in the new release and prompted users to upgrade.

On 2021-02-10 we received a CVE ID and published this advisory within a few hours of notification.

We would like to thank Alessandro for using responsible disclose to allow us to address the issue promptly and publish this advisory once an update was available that resolved the issue and Balázs Orbán (@balazsorban44) for facilitating a timely release of the fix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next-auth`	all versions	3.3.0`npm install next-auth@3.3.0`

Affected Products

1 product · 1 configurations

Application

next-authnextauth.js

< 3.3.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

NextAuth.js (next-auth) is am open source authentication solution for Ne…

github.comNVDFeb 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next-auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next-auth to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pg53-56cg-4m8q is resolved across your whole dependency graph.
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

### Impact Implementations using the **Prisma database adapter** with the **Email provider** **are impacted**. Implementations using the Prisma database adapter that are not using the Email provider are not impacted. Implementations using the default database adapter (TypeORM) with the Email provider are not impacted. Implementations not using a database are not impacted. ### Patches This issue is fixed in 3.3.0 and newer versions. ### Workarounds Those not able to upgrade can alternatively disable the Email provider as a workaround. ### Description The Prisma database adapter was chec

O3 Security · Impact-Aware SCA

Is GHSA-pg53-56cg-4m8q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Token verification bug in next-authGHSA-pg53-56cg-4m8q

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Description

Timeline

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-pg53-56cg-4m8q in your dependencies?