CVE-2025-67731: Aarondoran servify-express · Uncontrolled Resource Consumption
Affects Aarondoran servify-expressSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.2 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Dec 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.
What to do
Upgrade Aarondoran servify-express to 1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmservify-expresspkg:npm/servify-expressOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade servify-express to version 1.2 or later to apply the official fix. If upgrading is not immediately feasible, they should configure the express.json() middleware with a strict 'limit' parameter to cap the maximum JSON request body size (e.g., '100kb' or less depending on application needs). Implement application-level rate limiting to restrict the number of requests per client IP to prevent flooding. Deploy reverse proxies such as NGINX or HAProxy in front of the Node.js application to enforce maximum request body sizes and filter out oversized requests before they reach the application. Additionally, monitor server resource usage and logs for unusual spikes in request sizes or memory consumption. Conduct regular security audits of Node.js middleware configurations to ensure no unbounded parsers are exposed to untrusted clients. Finally, educate development teams on secure middleware configuration and the risks of default settings that may lead to resource exhaustion.
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.