CVE-2022-24858
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditednext-auth v3 users before version 3.29.2 are impacted. next-auth version 4 users before version 4.3.2 are also impacted. Upgrading to 3.29.2 or 4.3.2 will patch this vulnerability. If you are not able to upgrade for any reason, you can add a configuration to your callbacks option. If you already have a `redirect` callback, make sure that you match the incoming `url` origin against the `baseUrl`.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an open redirect vulnerability in next-auth's redirect callback. When the redirect callback does not validate that the incoming URL origin matches the application's baseUrl, attackers can craft malicious URLs to redirect authenticated users to arbitrary external sites, potentially leading to phishing attacks or session theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.0, < 3.29.2>= 4.0.0, < 4.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed next-auth versionRun `npm list next-auth` or inspect your package.json file to find the installed version of next-authAffected if The version is >= 3.0.0 and < 3.29.2, or >= 4.0.0 and < 4.3.2
-
Locate the NextAuth configuration fileFind the NextAuth API route handler, typically located at pages/api/auth/[...nextauth].js, pages/api/auth/[...nextauth].ts, or app/api/auth/[...nextauth]/route.js in your projectAffected if The file exists and handles authentication routing
-
Check for a custom redirect callbackInspect the NextAuth configuration object for a `callbacks` section containing a `redirect` callback functionAffected if No custom redirect callback is defined, meaning the default vulnerable callback is being used
-
Verify URL origin validation in redirect callbackIf a custom redirect callback exists, examine its code to confirm it validates the URL origin against the application's baseUrl before allowing the redirectAffected if Either no custom redirect callback is defined, OR a custom callback exists but does NOT validate that the redirect URL origin matches the expected baseUrl
You are affected if your next-auth version is in the vulnerable range AND you have not implemented a custom redirect callback that explicitly validates the URL origin against your baseUrl.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.29.24.3.2
Upgrade to next-auth v3.29.2 or v4.3.2, or implement a redirect callback that explicitly validates the url origin against the baseUrl before allowing redirects.
[email protected] for v3 users; [email protected] for v4 users
- Check your current next-auth version by running `npm list next-auth` or `yarn list next-auth`
- Identify your major version (v3 or v4) from the version number
- For v3 users: run `npm install [email protected]` or `yarn add [email protected]`
- For v4 users: run `npm install [email protected]` or `yarn add [email protected]`
- Verify the correct version is installed after upgrade
- Test authentication flows including sign-in and redirects
- If you cannot upgrade and use a redirect callback: ensure the callback validates that the incoming `url` origin matches your `baseUrl` to prevent open redirect attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24858 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data