CVSS 3.1
5.9 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCVE-2026-125332 Forge: TLS client crash on an unsupported ServerHello compression method
Medium (5.9) in digitalbazaar forge. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in node-forge 1.4.3.
On this page
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.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Under analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-125332 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125332?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125332?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125332 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-125332)
HTML:
<a href="https://cve.bz/cve/CVE-2026-125332"><img src="https://cve.bz/cve/badge/CVE-2026-125332.svg" alt="CVE-2026-125332"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| digitalbazaar forge | < 1.4.3 |
Fix and patched versions
node-forge(npm): fixed in 1.4.3
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-w4xr-hqv8-ch44 | npm | node-forge | <1.4.3 | 1.4.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 20.04:LTS, 22.04:LTS | node-node-forge | no fix listed | UBUNTU-CVE-2026-125332 |
| Azure Linux | 3 | python-tensorboard | no fix listed | AZL-113609 |
From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).