Arbitrary Code Injection Affecting next package, versions >=14.3.0-canary.77 <15.0.5>=15.1.0 <15.1.9>=15.2.0-canary.0 <15.2.6>=15.3.0-canary.0 <15.3.6>=15.4.0-canary.0 <15.4.8>=15.5.0 <15.5.7>=16.0.0-beta.0 <16.0.7
Threat Intelligence
Snyk has reported that there have been attempts or successful attacks targeting this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-NEXT-14173355
- published3 Dec 2025
- disclosed3 Dec 2025
- creditLachlan Davidson
Introduced: 3 Dec 2025
CVE-2025-55182 (opens in a new tab)How to fix?
Upgrade next to version 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7 or higher.
Overview
next is a react framework.
Affected versions of this package are vulnerable to Arbitrary Code Injection via unsafe deserialization of RSC payloads from HTTP requests to Server Function endpoints. An unauthenticated attacker can execute arbitrary code on the server by sending malicious HTTP requests.
Note:
Serverless applications and applications that do not use a framework, bundler, or bundler plugin that supports React Server Components are not affected by this vulnerability.
Next.js 13.x, Next.js 14.x stable, Pages Router applications, and the Edge Runtime are not affected.
This vulnerability originates in the upstream React implementation. This advisory tracks the downstream impact on Next.js applications using the App Router.
CVE-2025-66478 was originally announced for this vulnerability and later rejected as a duplicate of CVE-2025-55182.