Advisory

GHSA-qgc4-8p88-4w7m

Also known as: CVE-2025-67731

Summary

Servify-express rate limit issue

Details

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-12-11 18:36 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

servify-express

npm · All systems

Affected

  • introduced 0, fixed 1.2 (ecosystem)

Fixed versions

1.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences