Forge: TLS client crash on an unsupported ServerHello compression method
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.4.3.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 43/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 93% of node-forge downloads last week were affected versions (59.6M).npm, 63.7M downloads in the last 7 days, read Nov 10, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Forge (node-forge), a JavaScript implementation of TLS, has a flaw in its TLS client code where it accepts an unoffered compression method from the server. An attacker who can reach the client over the network, without logging in, can make the Node.js process crash by sending or altering the server's handshake message, causing a denial of service.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, a forge.tls client accepts a ServerHello compression_method that it did not offer. When the client later handles ServerHelloDone, tls.createConnectionState() rejects the unsupported compression algorithm by throwing an Error that propagates from connection.process(). A malicious server or an on-path attacker can alter the unauthenticated ServerHello compression byte before the server Finished message and terminate a Node.js process when the application does not catch the exception. The affected client paths include direct forge.tls use, forge.tls.wrapSocket, and forge.http; forge.tls servers are not affected, and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20node-forge: 55.6M downloads a week
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 48 if advisories confirm default setups are exposed
Impact
What to do
Upgrade to a fixed version: 1.4.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125332 (Forge: TLS client crash on an unsupported ServerHello compression method), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125332 (entry last updated 2026-11-10): Affected: - digitalbazaar forge: fixed in 1.4.3 - npm package node-forge: fixed in 1.4.3 Fixed versions: 1.4.3. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-125332 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125332 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (npm): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/digitalbazaar/forge/security/advisories/GHSA-w4xr-hqv8-ch44 - https://github.com/digitalbazaar/forge/pull/1169 - https://github.com/digitalbazaar/forge/commit/1d9816d333c23c523ef2bd8b24282c87db2654ef - https://github.com/digitalbazaar/forge/releases/tag/v1.4.3 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125332 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125332.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- digitalbazaar forge
fixed in 1.4.3
- node-forgenpm
fixed in 1.4.3
Fixed in 1.4.3 (released Nov 4, 2026, 6 days before disclosure).
The latest release, 1.4.3, is not affected.
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125332
Is CVE-2026-125332 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-125332?
forge: before 1.4.3. node-forge (npm): before 1.4.3.Source: cve.now feed data
How do I fix CVE-2026-125332?
Upgrade to a fixed version: 1.4.3.Source: cve.now feed data