# CVE-2026-125332: Forge: TLS client crash on an unsupported ServerHello compression method


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-w4xr-hqv8-ch44, MINI-3wj9-5gwv-qhv3, MINI-86j9-h6p3-xcpr, MINI-8x46-mhc5-v599, MINI-97qf-f422-7ch4, MINI-g8p8-v8v8-p26g, MINI-hhvf-49h7-554x, UBUNTU-CVE-2026-125332

## What is CVE-2026-125332?

CVE-2026-125332 is a medium-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 

### Official 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.

Weakness: CWE-248 (Uncaught Exception), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-125332?

1 open source package ship an affected version, including node-forge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-forge` | npm | All versions | 1.4.3 |

## How do I fix CVE-2026-125332?

Upgrade node-forge to 1.4.3 or later.

## Is CVE-2026-125332 being exploited?

There is no known exploitation of CVE-2026-125332 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125332 and fix it if it is affected.

What it is: CVE-2026-125332 is a medium-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125332 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-forge (npm): affected all versions; fixed in 1.4.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125332/ (Markdown: https://insights.sbomify.com/CVE-2026-125332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125332
- OSV: https://osv.dev/vulnerability/CVE-2026-125332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125332/
Summaries are generated and may contain mistakes; the official description above is the record.