Authorization bypass in Next.js
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| vercel | next.js | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Trusted Artifact Signer 1.1 | |||
| registry.redhat.io/rhtas/rekor-search-ui-rhel9:sha256:571c48ecb2658ce70199c06dc483ea48a16e032a764a6830388ad845f508d981 | cpe:/a:redhat:trusted_artifact_signer:1.1::el9 | RHSA-2025:3807 | 2025-04-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-7gfc-8cq8-jh5f | Next.js authorization bypass vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 4.0% (3.995% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vercel
Vercel next.js |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Vercel
Vercel next.js |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat trusted Artifact Signer |
|
| CPEs | cpe:/a:redhat:trusted_artifact_signer:1.1::el9 | |
| Vendors & Products |
Redhat
Redhat trusted Artifact Signer |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability. | |
| Title | Authorization bypass in Next.js | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV3_1
|