Authorization bypass in Next.js
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Partial Red Hat: 1 fixed, 2 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-285.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| vercel | next.js | 9.5.5 to before 14.2.15 | 14.2.15 | Patch available | CNA |
| — | next (npm) | 9.5.5 to before 14.2.15 | 14.2.15 | Patch available | GHSA-7gfc-8cq8-jh5f |
- next.js Vendorvercel Affected 9.5.5 to before 14.2.15 Fixed in 14.2.15 Patch available CNA
- next (npm) Vendor— Affected 9.5.5 to before 14.2.15 Fixed in 14.2.15 Patch available GHSA-7gfc-8cq8-jh5f
Remediation
- Fix · CNA next.js (vercel) Fixed in 14.2.15
- Fix · GHSA-7gfc-8cq8-jh5f next (npm) Fixed in 14.2.15 Advisory →
Red Hat 1 advisory
- RHSA-2025:3807 Released 2025-04-10 · Red Hat rating ModerateRHTAS 1.1.2 - Red Hat Trusted Artifact Signer Release
- Red Hat Trusted Artifact Signer 1.1 registry.redhat.io/rhtas/rekor-search-ui-rhel9
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Enterprise Linux 9 | Affected | No fix planned: Out of support scope |
| streams for Apache Kafka | Affected | No fix yet |
| Red Hat Trusted Artifact Signer 1.1 | Fixed | RHSA-2025:3807 |
Not affected: 3 products
- Red Hat Enterprise Linux 7
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9
Timeline
- 2026-10-02 Threatist record created from CVE-2024-51479
- 2026-10-03 Alias added: GHSA-7gfc-8cq8-jh5f
References
Advisory 2
More vercel Next.js vulnerabilities
- TI-2025-34861 Deserialization of untrusted data in Meta react-server-dom-webpack KEVCVSS 3.1CRITICAL 10.0
- TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
- TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
- TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
- TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
- TI-2026-32490 Next.js: Server-side request forgery in applications using WebSocket upgrades CVSS 3.1HIGH 8.6
Sources
- CVE-2024-51479 · CVE Program
- CVE-2024-51479 · NVD
- FIRST EPSS
- GHSA-7gfc-8cq8-jh5f · GitHub Advisory Database · CC BY 4.0
- CVE-2024-51479 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences