CVE-2026-64649
Next.js: Server-Side Request Forgery in Server Actions on Custom Servers
Reported by github_m · Published July 27, 2026
next is fixed in 16.2.11 and 15.5.21 (npm)
Next.js is a React framework for building full-stack web applications. In versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10, when a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization. Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward. This issue has been fixed in versions 15.5.21 and 16.2.11.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| next | npm | 16.2.11, 15.5.21 |
| langfuse-2 | Chainguard | 2.95.12-r35 |
| langfuse-fips-3 | Chainguard | 3.224.1-r0 |
| langfuse-fips-2 | Chainguard | 2.95.12-r38 |
| jitsucom-jitsu | Chainguard | 2.11.0-r30 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| vercel | next.js | >= 14.1.1, < 15.5.21, >= 16.0.0 < 16.2.11 |
| chainguard | langfuse-2 | 0 |
| npm | next | 16.0.0, 14.1.1 |
| chainguard | langfuse-fips-3 | 0 |
| chainguard | langfuse-fips-2 | 0 |
| chainguard | jitsucom-jitsu | 0 |
| vercel | next.js | 16.0.0, 14.1.1 |
| chainguard | cadence-web | 0 |
| chainguard | homepage | 0 |
| chainguard | langfuse-3 | 0, 0 |
| wolfi | jitsucom-jitsu | 0 |
| chainguard | peerdb-ui | 0 |
| wolfi | langfuse-3 | 0, 0 |
| chainguard | keep-fips | 0 |
| chainguard | keep | 0 |
Timeline
- Jul 21, 2026 CVE Published
- Jul 28, 2026 Coalition ESS Score
- Jul 28, 2026 Security Advisory (2 in total, the first dated here)
- Jul 28, 2026 CVE Updated
- Aug 7, 2026 EPSS Score (30 in total, the first dated here)
- Aug 13, 2026 Distribution Patch
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-64649
vulnetix vdb fixes CVE-2026-64649
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-64649/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x x_refsource_CONFIRM
- https://github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b x_refsource_MISC
- https://github.com/vercel/next.js/commit/e3e5666ccead3a15162793d697af5e48b7cc0498 x_refsource_MISC
- https://github.com/vercel/next.js/releases/tag/v15.5.21 x_refsource_MISC
- https://github.com/vercel/next.js/releases/tag/v16.2.11 x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2026-64649 advisory
- https://github.com/advisories/GHSA-89xv-2m56-2m9x advisory