# CVE-2022-31093: Improper Handling of `callbackUrl` parameter in next-auth

> An attacker can cause a denial of service and login failures by sending a malformed callbackUrl parameter to NextAuth.js applications.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-g5fm-jp9v-2432

## What is CVE-2022-31093?

CVE-2022-31093 is a high-severity denial of service vulnerability in nextauthjs next-auth, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NextAuth.js is a complete open source authentication solution for Next.js applications. In affected versions an attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally is converted to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to the **API route handler timing out and logging in to fail**. This has been remedied in versions 3.29.5 and 4.5.0. If for some reason you cannot upgrade, the workaround requires you to rely on Advanced Initialization. Please see the documentation for more.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2022-31093?

4 open source packages ship an affected version, including next-auth. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next-auth` | npm | All versions | 3.29.5 |
| `next-auth` | npm | All versions | 3.29.5 |
| `next-auth` | npm | From 4.0.0 | 4.5.0 |
| `next-auth` | npm | From 4.0.0 | 4.5.0 |

Products: Nextauth.js Next-Auth.

## How do I fix CVE-2022-31093?

Upgrade next-auth to a fixed version for your release line: 3.29.5 or 4.5.0.

## Is CVE-2022-31093 being exploited?

There is no known exploitation of CVE-2022-31093 in the wild and no public exploit code.

## Other vulnerabilities in nextauthjs next-auth

- [CVE-2022-35924](https://insights.sbomify.com/CVE-2022-35924/): Verification requests (magic link) sent to unwanted emails (critical 9.1)
- [CVE-2023-27490](https://insights.sbomify.com/CVE-2023-27490/): Missing proper state, nonce and PKCE checks for OAuth authentication in next-auth (high 8.1)
- [CVE-2022-31127](https://insights.sbomify.com/CVE-2022-31127/): Improper handling of email input in next-auth (high 7.1)
- [CVE-2022-39263](https://insights.sbomify.com/CVE-2022-39263/): NextAuth.js Upstash Adapter missing token verification (medium 6.8)
- [CVE-2022-29214](https://insights.sbomify.com/CVE-2022-29214/): URL Redirection to Untrusted Site ('Open Redirect') in next-auth (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31093 and fix it if it is affected.

What it is: CVE-2022-31093 is a high-severity denial of service vulnerability in nextauthjs next-auth, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31093 in the wild and no public exploit code.

Affected packages and fixed versions:
- next-auth (npm): affected all versions; fixed in 3.29.5
- next-auth (npm): affected all versions; fixed in 3.29.5
- next-auth (npm): affected from 4.0.0; fixed in 4.5.0
- next-auth (npm): affected from 4.0.0; fixed in 4.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31093/ (Markdown: https://insights.sbomify.com/CVE-2022-31093/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31093
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31093
- OSV: https://osv.dev/vulnerability/CVE-2022-31093

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31093/
Summaries are generated and may contain mistakes; the official description above is the record.