EM-20261030-S9AK
VulnerabilityHigh severity
node-forge Vulnerability (CVE-2026-119187)
CVE-2026-119187
Status
Developing
Since : signals keep joining.
- First Signal
- Oct 29 19:19 UTCC41 Red Hat Security Data
- Page Born
- Oct 30 23:01 UTCsecond source joined
- Last Signal
- Oct 30 23:01 UTC5 days before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 6 daysso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedOct 29 19:19 UTCC41 first to name it
- Scored: reachedOct 29 19:19 UTCNo CVSS yet · EPSS 0.4%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedOct 29 19:19 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-hqq3-7jhf-c5jx / CVE-2026-119187: Forge: Denial of ervice in TLS record proce ing via call tack exhau tion (opens source in a new tab) npm:node-forge High severityDatabaseC26 GitHub Advisory Database
- Red Hat: CVE-2026-119187 (important) (opens source in a new tab) node-forge: node-forge: Denial of Service via call stack exhaustion in TLS record processing High severityVendorC41 Red Hat Security Data