---
id: "CVE-2026-125332"
page: "https://infrastack.ai/live/CVE-2026-125332"
kind: "vulnerability"
aliases: ["CVE-2026-125332"]
title: "node-forge: malformed TLS ServerHello can crash Node.js client processes"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["javascript", "node-forge", "node.js", "package"]
not_affected_if: ["exceptions-caught", "server-only-use"]
published_at: "2026-11-10T19:21:10+00:00"
first_seen_at: "2026-11-10T19:25:14+00:00"
updated_at: "2026-11-10T19:59:54+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-125332", "first_seen_at": "2026-11-10T19:25:14+00:00"}]
exploit_sources: []
---

# node-forge: malformed TLS ServerHello can crash Node.js client processes

Link for people: https://infrastack.ai/live/CVE-2026-125332 (this .md is for agents)

A forge.tls client accepts a ServerHello compression value it never offered, then throws an uncaught error when handling ServerHelloDone. A malicious server or on-path attacker can use this to terminate a Node.js process that does not catch the exception.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version with `npm ls node-forge` and look for any version below `1.4.3`.
- Search the codebase for `forge.tls`, `forge.tls.wrapSocket` or `forge.http` usage in client code.

## Fix

- node-forge: upgrade to `1.4.3`

## Timeline

- 2026-11-10T19:25:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-125332

## Documents

- [advisory] Vendor advisory: github.com https://github.com/digitalbazaar/forge/security/advisories/GHSA-w4xr-hqv8-ch44
- [fix] Patch: github.com https://github.com/digitalbazaar/forge/commit/1d9816d333c23c523ef2bd8b24282c87db2654ef
- [fix] Release notes: github.com https://github.com/digitalbazaar/forge/releases/tag/v1.4.3

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_