Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · Low · None
- Fix status
- Partial Red Hat: 1 fixed, 1 without a fix
Attack profile from CVSS 4.0 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-601.
Summary
Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a rewrites() or redirects() rule that builds its external destination hostname from request-controlled input can be pointed at an arbitrary hostname, regardless of the rule's hostname suffix. For a rewrite, Next.js proxies the request to that arbitrary host and serves the response from the application's origin, leading to Server-Side Request forgery. A redirects() rule configured this way is vulnerable to an Open Redirect. This issue has been fixed in versions 15.5.21 and 16.2.11.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- 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 | >= 12.0.0 < 15.5.21; 16.0.0 to before 16.2.11 | 16.2.11 | Patch available | CNA |
| — | next (npm) | 12.0.0 to before 15.5.21 | 15.5.21 | Patch available | GHSA-p9j2-gv94-2wf4 |
| — | next (npm) | 16.0.0 to before 16.2.11 | 16.2.11 | Patch available | GHSA-p9j2-gv94-2wf4 |
- next.js Vendorvercel Affected >= 12.0.0 < 15.5.21; 16.0.0 to before 16.2.11 Fixed in 16.2.11 Patch available CNA
- next (npm) Vendor— Affected 12.0.0 to before 15.5.21 Fixed in 15.5.21 Patch available GHSA-p9j2-gv94-2wf4
- next (npm) Vendor— Affected 16.0.0 to before 16.2.11 Fixed in 16.2.11 Patch available GHSA-p9j2-gv94-2wf4
Remediation
- Fix · CNA next.js (vercel) Fixed in 16.2.11
- Fix · GHSA-p9j2-gv94-2wf4 next (npm) Fixed in 15.5.21 Advisory →
- Fix · GHSA-p9j2-gv94-2wf4 next (npm) Fixed in 16.2.11 Advisory →
Red Hat 1 advisory
- RHSA-2026:54435 Released 2026-08-12 · Red Hat rating ImportantStreams for Apache Kafka 3.2.1 release and security update
- Streams for Apache Kafka 3.2.1
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Enterprise Linux AI (RHEL AI) 3 | Affected | No fix yet |
| Streams for Apache Kafka 3.2.1 | Fixed | RHSA-2026:54435 |
Not affected: 6 products
- Red Hat Enterprise Linux 10
- Red Hat Enterprise Linux 7
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9
- Red Hat Trusted Artifact Signer
- streams for Apache Kafka 2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-64645
- 2026-10-03 Alias added: GHSA-p9j2-gv94-2wf4
- 2026-11-03 Affected versions changed · Red Hat
References
Patch 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-2026-64645 · CVE Program
- CVE-2026-64645 · NVD
- FIRST EPSS
- GHSA-p9j2-gv94-2wf4 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-64645 · 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