Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-hqq3-7jhf-c5jx

Forge: Denial of service in TLS record processing via call stack exhaustion

CVSS 7.5 HighEPSS 0.0042 · 35th percentile

Published by the GitHub Advisory Database at 30 Oct 2026, 23:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
node-forgenpm<1.4.11.4.1
Identifiers
GHSA-hqq3-7jhf-c5jx · CVE-2026-119187
Weakness (CWE)
CWE-674
Tags
Published
30 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected: the node-forge npm package, versions below 1.4.1. In TLS record processing, connections from forge.tls.createConnection() handle received records recursively, so one chunk containing thousands of small records (such as heartbeat records, which are accepted before the handshake) can exhaust the call stack. An unauthenticated peer that can connect to a forge TLS endpoint can send such a chunk, causing a RangeError that crashes Node.js processes using the documented socket wiring. Upgrade to node-forge 1.4.1, which processes records in a loop.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0042, the 35th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 29 Oct 2026, 19:19 UTC Confirmed by the CVE List
  2. 29 Oct 2026, 20:17 UTC Confirmed by NVD
  3. 31 Oct 2026, 13:32 UTC First seen by agentprime
  4. 31 Oct 2026, 13:32 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.