CVE-2025-57822VulnerabilityPublished 29 Aug 2025Updated 2 Sep 2025

CVE-2025-57822: vercel next.js · Server-Side Request Forgery (SSRF)

Affects vercel next.jsSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 6.5 Medium : upgrade to 15.4.7 or 14.2.32 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.5% chance of exploitation in 30 days – higher than 85% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.4.7, 14.2.32

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Aug 2025
Detectable: evidence found.
nuclei template: Next.js Middleware - Server-Side Request Forgery
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vercel next.js to 15.4.7 or 14.2.32.

Affected software

Product	Affected	Fixed in
vercel next.js	Affected <14.2.32 <15.4.7	Fixed in 14.2.32 15.4.7

AI-suggested

1. Upgrade Next.js to versions 14.2.32 or 15.4.7 or later immediately to incorporate the official fix. 2. Conduct a thorough audit of all custom middleware implementations to ensure that the next() function is always called with the explicit request object, avoiding implicit forwarding of user-supplied headers. 3. Implement strict validation and sanitization of all headers and user inputs that influence internal requests. 4. Employ network segmentation and internal access controls to limit the exposure of sensitive internal endpoints, reducing the impact of potential SSRF exploitation. 5. Monitor application logs for unusual internal request patterns that may indicate SSRF attempts. 6. Use Web Application Firewalls (WAFs) with rules tailored to detect and block SSRF attack patterns targeting Next.js applications. 7. Educate development teams about secure middleware practices and the risks of SSRF to prevent similar issues in future code.

Description

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.

Impact

For European organizations, the impact of this SSRF vulnerability can be significant, especially for those relying on Next.js for internal or customer-facing web applications. Exploitation could allow attackers to access sensitive internal services, databases, or metadata endpoints that are otherwise protected by network segmentation or firewalls. This could lead to unauthorized disclosure of confidential information, including personal data protected under GDPR, intellectual property, or internal configuration details. The partial integrity impact means attackers might manipulate some internal requests, potentially leading to further exploitation or pivoting within the network. While availability is not directly affected, the breach of confidentiality alone can result in regulatory penalties, reputational damage, and financial losses. The medium severity score suggests that exploitation is not trivial but feasible, emphasizing the need for proactive patching and code review. Organizations with complex middleware or custom header forwarding logic are at higher risk. Given the widespread adoption of Next.js in Europe’s tech sector, especially among startups and enterprises building modern web applications, the threat is relevant and should be addressed promptly.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Sep 2025, 00:35 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats