VulnerabilityPublished 30 May 2025Updated 13 Jun 2025

CVE-2025-48068: vercel next.js · Missing Origin Validation in WebSockets

Affects vercel next.jsSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low : upgrade to 15.2.2 or 14.2.30 when convenient.

Data as of 27 Oct 2026, 05:11 UTC

CVSS 4.0 base score

2.3Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.2.2, 14.2.30

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
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 26 Oct 2026.

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 or the CVSS exploit maturity 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 next to 15.2.2 or 14.2.30.

Affected software

Product	Affected	Fixed in
npmnext`pkg:npm/next`Other threats	Affected >=13.0.0 <14.2.30 =15.0.0 <15.2.2	Fixed in 14.2.30 15.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should take the following specific actions: 1) Upgrade all Next.js development environments to version 14.2.30 or later, or 15.2.2 or later, where the vulnerability is patched. 2) Educate developers about the risks of running development servers exposed to untrusted networks or visiting unknown websites while the dev server is active. 3) Implement network segmentation or firewall rules to restrict access to development servers, ensuring they are not reachable from external or untrusted networks. 4) Use secure development practices such as running development environments within isolated containers or virtual machines to limit exposure. 5) Monitor developer workstations for unusual network activity during development sessions. 6) Encourage the use of VPNs or secure tunnels when remote development is necessary to reduce exposure to malicious web content. 7) Incorporate security scanning tools in the development pipeline to detect outdated dependencies and enforce timely updates. These measures go beyond generic advice by focusing on controlling the development environment exposure and developer behavior, which are critical given the nature of this vulnerability.

Description

Next.js is a React framework for building full-stack web applications. In versions starting from 13.0 to before 14.2.30 and 15.0.0 to before 15.2.2, Next.js may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active. This issue has been patched in versions 14.2.30 and 15.2.2.

Impact

For European organizations, the impact of CVE-2025-48068 is relatively low but still noteworthy. Since the vulnerability only affects local development environments and requires user interaction (visiting a malicious webpage), the risk of widespread exploitation is limited. However, organizations with active development teams using vulnerable Next.js versions could face limited source code exposure, potentially leaking proprietary or sensitive application logic. This could aid attackers in crafting more effective attacks against production systems if the leaked code contains security flaws or sensitive business logic. The impact is primarily on confidentiality, with no direct effect on integrity or availability. Given the vulnerability does not affect production deployments, operational disruption is unlikely. Nonetheless, organizations with strict data protection requirements or intellectual property concerns should consider this vulnerability seriously to prevent inadvertent leaks during development. The low CVSS score aligns with the limited impact, but the risk is amplified if developers are not aware of the need to update or avoid visiting untrusted websites during development.

CWE-1385Missing Origin Validation in WebSockets (opens in a new tab)
Variant weakness
The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.
Implementation
Enable CORS-like access restrictions by verifying the 'Origin' header during the WebSocket handshake.
Implementation
Use a randomized CSRF token to verify requests.
Implementation
Use TLS to securely communicate using 'wss' (WebSocket Secure) instead of 'ws'.
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (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 Jul 2025, 21:27 UTC

WeaknessesCWE-1385

Technical details

References

Community reviews

Related threats