CVE-2025-67731

Source
https://cve.org/CVERecord?id=CVE-2025-67731
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-67731.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-67731
Aliases
Published
2025-12-12T07:40:53.047Z
Modified
2026-03-14T12:45:57.304098Z
Severity
  • 8.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CVSS Calculator
Summary
Servify Express does not enforce rate limiting when parsing JSON
Details

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.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/67xxx/CVE-2025-67731.json",
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-400"
    ]
}
References

Affected packages

Git / github.com/aarondoran/servify-express

Affected ranges

Type
GIT
Repo
https://github.com/aarondoran/servify-express
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
Type
GIT
Repo
https://github.com/aarondoran/servify-express
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

V1.*
V1.1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-67731.json"