CVE-2025-67731: Servify express Servify-express Rate Limit Issue Vulnerability

HIGH
Advisory Identifier: GHSA-qgc4-8p88-4w7m
Share
CWE-770
Published
Advisory Summary

CVE-2025-67731 is a HIGH servify-express rate limit issue vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Servify express libraries in the npm ecosystem. The issue involves servify-express rate limit issue. Remediation is available by upgrading affected packages to version 1.2.

CVE-2025-67731 at a Glance

CVE Identifier CVE-2025-67731
GHSA Identifier GHSA-qgc4-8p88-4w7m
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Servify express
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-67731

To remediate this vulnerability, upgrade all affected Servify express dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

servify-express fixed: 1.2 
npm install servify-express@1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls servify-express

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-67731, inspect your project dependencies using npm:

npm ls servify-express

Analyze the terminal output to locate any version of Servify express in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2), your application is affected.

Note: The npm ls servify-express command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Servify express, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact The Express server uses `express.json()` without a size limit, which can allow attackers to send extremely large request bodies. This may lead to 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. ### Patches This issue is not a flaw in Express itself but in configuration. Users should set a request-size limit when enabling the JSON body parser. For example: `app.use(express.json({ limit: "100kb" }));` ### Workarounds Users can mitigate the issue without upgrading by: - Adding a `limit` option to the JSON parser - Implementing rate limiting at the application or reverse-proxy level - Rejecting unusually large requests before parsing - Using a reverse proxy (such as NGINX) to enforce maximum request body sizes

CVE-2025-67731 Affected Servify express Versions

1 component(s)
Fixed Versions:
1.2
Product / Package Ecosystem Affected Versions Fixed Version
servify-express
npm/servify-express
npm
< 1.2
1.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m
NVD — CVE-2025-67731 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-67731
Security Fix Commit FIX COMMIT
https://github.com/Aarondoran/servify-express/commit/197d848e5450bf85b0dd19ef8c2aa4ba96192300
Security Fix Commit FIX COMMIT
https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61
Servify express Source Repository REPOSITORY
https://github.com/Aarondoran/servify-express
Servify express Release RELEASE
https://github.com/Aarondoran/servify-express/releases/tag/V1.2

Frequently Asked Questions

What is CVE-2025-67731?
CVE-2025-67731 is a security vulnerability in Servify express involving Servify-express rate limit issue under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Servify express versions are affected?
Affected versions include releases prior to 1.2 across affected packages: servify-express.
What version fixes CVE-2025-67731?
Upgrading to 1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is servify-express affected?
Yes, servify-express is affected in releases prior to 1.2. Upgrade your dependency to 1.2 or later.
What CWE is associated with CVE-2025-67731?
CVE-2025-67731 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check npm dependencies for CVE-2025-67731?
Run the dependency tree command: 'npm ls servify-express'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qgc4-8p88-4w7m",
  "modified" : "2025-12-12T16:12:24Z",
  "published" : "2025-12-11T18:36:54Z",
  "aliases" : [ "CVE-2025-67731" ],
  "summary" : "Servify-express rate limit issue",
  "details" : "### Impact\nThe Express server uses `express.json()` without a size limit, which can allow attackers to send extremely large request bodies. This may lead to 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.\n\n### Patches\nThis issue is not a flaw in Express itself but in configuration. Users should set a request-size limit when enabling the JSON body parser. For example:\n`app.use(express.json({ limit: \"100kb\" }));`\n\n### Workarounds\nUsers can mitigate the issue without upgrading by:\n- Adding a `limit` option to the JSON parser\n- Implementing rate limiting at the application or reverse-proxy level\n- Rejecting unusually large requests before parsing\n- Using a reverse proxy (such as NGINX) to enforce maximum request body sizes",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "servify-express"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67731"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Aarondoran/servify-express/commit/197d848e5450bf85b0dd19ef8c2aa4ba96192300"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Aarondoran/servify-express"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Aarondoran/servify-express/releases/tag/V1.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-11T18:36:54Z",
    "nvd_published_at" : "2025-12-12T08:15:48Z"
  }
}