Forge: TLS client crash on a handshake record received without a session

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary A `forge.tls` client throws an uncaught `TypeError` from `connection.process()` when it receives a ServerHello while it has no session: after a `close_notify` alert or a call to `close()`, or before `handshake()` is called. A malicious server or an on-path attacker can use this to terminate a Node.js process. Fixed in node-forge 1.4.3.

Details `tls.handleHandshake()` in `lib/tls.js` updates the handshake digests with `c.session.md5.update(bytes)` before it calls the message handler. A client creates its session in `handshake()`, and `c.reset()` sets it to `null` when the connection is closed. Closing doesn't set the fail flag, and the client goes back to expecting a ServerHello, so a Handshake record received afterwards still reaches `handleHandshake()`, which throws `TypeError: Cannot read properties of null (reading 'md5')`. This happens: - after the server sends a `close_notify` alert (at any alert level); - after the application calls `close()`; - before the…

Published by the source

10 Nov 2026, 21:14 UTC

Last modified by the source

10 Nov 2026, 21:30 UTC

Source last checked

11 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 11 Nov 2026

   Amended from osv record GHSA-j8rw-jp99-435v

2. Revision 1 · created · 10 Nov 2026

   Published from ghsa record GHSA-j8rw-jp99-435v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-125334

Advisory: Forge: TLS client crash on a handshake record received without a session
IDs: CVE-2026-125334, GHSA-j8rw-jp99-435v
Record: https://patchnext.com/advisories/cve-2026-125334 (revision 2, source checked 11 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node-forge 1.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-forge: affected < 1.4.3; fixed in 1.4.3

## Suggested inspection (read-only)
- `npm ls node-forge --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-forge.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j8rw-jp99-435v (GitHub-reviewed advisory GHSA-j8rw-jp99-435v lists affected ranges: npm node-forge >=0 <=1.4.2)
- Verified: https://osv.dev/vulnerability/GHSA-j8rw-jp99-435v (OSV record GHSA-j8rw-jp99-435v lists affected ranges: npm node-forge >=0 <1.4.3 (fixed))

Commands are suggestions: review each one before running it.