An attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly thereby keeping the connection and associated…

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2019-5737: 16.18% estimated exploitation activity in the next 30 days; percentile 96.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly thereby keeping the connection and associated resources alive for a long period of time. Attack potential is mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active release lines including 6, 8, 10 and 11.

Published by the source

28 Feb 2019, 00:00 UTC

Last modified by the source

28 Feb 2019, 00:00 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 2 · published · 26 Oct 2026

   Published from vendor_advisory record nodejs-security-wg:core:60

2. Revision 1 · created · 26 Oct 2026

   Created from vendor_advisory record nodejs-security-wg:core:60

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-5737

Advisory: An attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly thereby keeping the connection and associated…
IDs: CVE-2019-5737
Record: https://patchnext.com/advisories/cve-2019-5737 (revision 2, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node 11.10.1, 10.15.2, 8.15.1, 6.17.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- runtime node: affected >= 6.0.0, < 6.17.0; >= 8.0.0, < 8.15.1; >= 10.0.0, < 10.15.2; >= 11.0.0, < 11.10.1; fixed in 11.10.1, 10.15.2, 6.17.0, 8.15.1

## Suggested inspection (read-only)
- runtime node: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://nodejs.org/dist/index.json (The nodejs.org release index dates the first patched release for CVE-2019-5737 to 2019-02-28.)
- Verified: https://raw.githubusercontent.com/nodejs/security-wg/main/vuln/core/60.json (Node.js security working group core entry 60 lists CVE-2019-5737 affecting node >=6.0.0 =8.0.0 =10.0.0 =11.0.0 <11.10.1)

Commands are suggestions: review each one before running it.