Deserialization of Untrusted Data Affecting next package, versions >=14.2.34 <14.2.35>=15.0.6 <15.0.7>=15.1.10 <15.1.11>=15.2.7 <15.2.8>=15.3.7 <15.3.8>=15.4.9 <15.4.10>=15.5.8 <15.5.9>=16.0.9 <16.0.10>=16.1.0-canary.0 <16.1.0-canary.19

next is a react framework.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to unsafe deserialization of payloads from HTTP requests to Server Function endpoints. An attacker can cause the server process to enter an infinite loop and hang, preventing it from serving future HTTP requests by sending specially crafted payloads.

Note:

This is caused by an incomplete fix for CVE-2025-55184.

Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.

Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.

• Facebook Security Advisory
• GitHub Commit
• GitHub PR
• React Blog Post
• Vercel Advisory