Cyber Resilience

CVE-2025-48068

Vercel Next.Js 13.0.0 – 14.2.30

Published
30 May 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 2.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0017 7th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2025-48068 is a low-severity Missing Origin Validation in WebSockets (CWE-1385) vulnerability in Vercel Next.Js. Its CVSS base score is 2.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-1385

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-27977Same product: Vercel Next.Js
CVE-2026-44576Same product: Vercel Next.Js
CVE-2025-57822Same product: Vercel Next.Js
CVE-2025-49826Same product: Vercel Next.Js
CVE-2026-27978Same product: Vercel Next.Js
CVE-2026-44580Same product: Vercel Next.Js
CVE-2026-29057Same product: Vercel Next.Js
CVE-2026-44578Same product: Vercel Next.Js
CVE-2024-46982Same product: Vercel Next.Js
CVE-2026-64649Same product: Vercel Next.Js

Affected Assets

vercel
next.js
13.0.0 — 14.2.30 · 15.0.0 — 15.2.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V4.4.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces approved authorizations on logical access, which can include origin checks before accepting WebSocket connections.

AC-4 Information Flow Enforcement good match

Enforces information flow policies that can require validation of communication origins at system boundaries.

SC-23 Session Authenticity good match

Protects authenticity of communications sessions, which origin validation helps ensure for WebSocket handshakes.

SC-7 Boundary Protection partial match

Monitors and controls communications at external interfaces, directly supporting origin validation for inbound WebSocket traffic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices directly require origin validation for WebSocket endpoints.

PR.AA-03 mostly match
prevents

Origin validation is a required step when authenticating WebSocket connection requests.

PR.AA-05 partial match
prevents

Enforcing authorization policy on incoming connections can require origin checks.

PR.IR-01 partial match
prevents

Network-level controls that block unauthorized logical access can mitigate missing origin checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing origin validation in WebSocket implementations.

A.8.20 Networks security partial match
degrades

Network security controls can enforce origin validation and restrict WebSocket connections to trusted sources.

A.8.21 Security of network services partial match
degrades

Secure configuration of network services can include origin checks for WebSocket endpoints.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate origin validation for WebSocket communications.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles can require proper origin validation mechanisms in WebSocket implementations.

A.8.28 Secure coding partial match
prevents

Secure coding standards can explicitly require origin validation for WebSocket connections.

References