EM-20261110-H97D VulnerabilityMedium severity

Forge Vulnerability (CVE-2026-125333)

CVE-2026-125333

Status

Developing

Since Nov 10 21:16 UTC: signals keep joining.

First Signal: Nov 10 18:48 UTCC41 Red Hat Security Data
Page Born: Nov 10 21:16 UTCsecond source joined
Last Signal: Nov 10 21:16 UTC26 hours before snapshot
Sources: 21 official · 1 research, news or crowd
Open For: 18 hoursso far

Life Of This Page

1
Born

Nov 10 21:16 UTC
A second, independent source names it.
2
Developing · Now

Nov 10 21:16 UTC
New signals join; severity can move.
3
Confirmed

Not yet
CISA KEV lists it, or exploitation in the wild is reported.
4
Resolved

Not yet
Past the fix deadline and 14 days with no new signal.
5
Archived

Not yet
30 days after resolved. Read only; the link keeps working. Reopens if it comes back.

The ID never changes, and earlier addresses keep working. 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: reached

Nov 10 19:21 UTC
C6 NVD published
Scored: reached

Nov 10 19:21 UTC
CVSS 5.9
Exploited: not yet

Not yet
No exploitation reported
Advisories: not yet

Not yet
None yet
Vendor Response: reached

Nov 10 18:48 UTC
C41 published
Resolved: not yet

Not yet
After 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

Nov 10 21:16 UTCGHSA-6cv4-p8m7-4r25 / CVE-2026-125333: Forge: ReDoS in forge.http response header and cookie trimming (opens source in a new tab) npm:node-forge Med severityDatabaseC26 GitHub Advisory Database
Nov 10 18:48 UTCRed Hat: CVE-2026-125333 (moderate) (opens source in a new tab) node-forge: node-forge: Denial of Service via inefficient regular expression in HTTP header parsing Med severityVendorC41 Red Hat Security Data