CVE-2025-57822

What it is

Next.js is a React framework for building full-stack web applications. Prior to versions 14.2.32 and 15.4.7, when next() was used without explicitly passing the request object, it could lead to SSRF in self-hosted applications that incorrectly forwarded user-supplied headers. This vulnerability has been fixed in Next.js versions 14.2.32 and 15.4.7. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

2.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-08-29 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-18 21:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.6% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-08-29 22:15 UTC

Last modified

2026-10-18 21:10 UTC

Exploit probability

2.6% · EPSS, next 30 days

Weakness

CWE-918 · Server-side request forgery

Record status

Analyzed

Affected

• Vercel next.js < 14.2.32
• Vercel next.js < 15.4.7

Attack profile CVSS 3.1 · 6.5

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-57822.md and follow it. Check whether this project is affected by CVE-2025-57822. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge