CVE-2025-67731
Servify Express does not enforce rate limiting when parsing JSON
Description
Servify Express is a Node.js package to start an Express server and log the port it's running on. Prior to 1.2, the Express server used express.json() without a size limit, which could allow attackers to send extremely large request bodies. This can cause excessive memory usage, degraded performance, or process crashes, resulting in a Denial of Service (DoS). Any application using the JSON parser without limits and exposed to untrusted clients is affected. The issue is not a flaw in Express itself, but in configuration. This issue is fixed in version 1.2. To work around, consider adding a limit option to the JSON parser, rate limiting at the application or reverse-proxy level, rejecting unusually large requests before parsing, or using a reverse proxy (such as NGINX) to enforce maximum request body sizes.
INFO
Published Date :
Dec. 12, 2025, 8:15 a.m.
Last Modified :
Oct. 7, 2026, 8:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 4.0 | HIGH | [email protected] |
Solution
- Update to Servify Express version 1.2 or later.
- Limit JSON parser body size.
- Implement request size limits at proxy.
- Reject oversized requests before parsing.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-67731.
| URL | Resource |
|---|---|
| https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61 | Patch |
| https://github.com/Aarondoran/servify-express/releases/tag/V1.2 | Product Release Notes |
| https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m | Mitigation Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-67731 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-67731
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-67731 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-67731 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 07, 2026
Action Type Old Value New Value Added Translation Title: servify-express de Aarondoran, Description: Servify Express es un paquete de Node.js para iniciar un servidor Express y registrar el puerto en el que se está ejecutando. Antes de la versión 1.2, el servidor Express utilizaba express.json() sin un límite de tamaño, lo que podría permitir a los atacantes enviar cuerpos de solicitud extremadamente grandes. Esto puede causar un uso excesivo de memoria, un rendimiento degradado o fallos en el proceso, lo que resulta en una Denegación de Servicio (DoS). Cualquier aplicación que utilice el analizador JSON sin límites y esté expuesta a clientes no confiables se ve afectada. El problema no es una falla en Express en sí, sino en la configuración. Este problema está solucionado en la versión 1.2. Para solucionarlo, considere añadir una opción de límite al analizador JSON, limitar la tasa a nivel de aplicación o de proxy inverso, rechazar solicitudes inusualmente grandes antes del análisis, o utilizar un proxy inverso (como NGINX) para aplicar tamaños máximos de cuerpo de solicitud. -
CVE Modified by [email protected]
Jun. 17, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'Aarondoran', 'product': 'servify-express', 'versions': [{'status': 'affected', 'version': '< 1.2'}]}] -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 17, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2025-67731', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2025-12-12T20:43:59.650020Z'} -
Initial Analysis by [email protected]
Mar. 17, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Added CPE Configuration OR *cpe:2.3:a:servify-express.js:servify_express:*:*:*:*:*:node.js:*:* versions up to (excluding) 1.2 Added Reference Type GitHub, Inc.: https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61 Types: Patch Added Reference Type GitHub, Inc.: https://github.com/Aarondoran/servify-express/releases/tag/V1.2 Types: Product, Release Notes Added Reference Type GitHub, Inc.: https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m Types: Mitigation, Vendor Advisory -
New CVE Received by [email protected]
Dec. 12, 2025
Action Type Old Value New Value Added Description Servify Express is a Node.js package to start an Express server and log the port it's running on. Prior to 1.2, the Express server used express.json() without a size limit, which could allow attackers to send extremely large request bodies. This can cause excessive memory usage, degraded performance, or process crashes, resulting in a Denial of Service (DoS). Any application using the JSON parser without limits and exposed to untrusted clients is affected. The issue is not a flaw in Express itself, but in configuration. This issue is fixed in version 1.2. To work around, consider adding a limit option to the JSON parser, rate limiting at the application or reverse-proxy level, rejecting unusually large requests before parsing, or using a reverse proxy (such as NGINX) to enforce maximum request body sizes. Added CVSS V4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/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 Added CWE CWE-400 Added Reference https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61 Added Reference https://github.com/Aarondoran/servify-express/releases/tag/V1.2 Added Reference https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m