Back to list

Forge: TLS client crash when the server sends no certificate — GHSA-525V-9GP9-W22H

GitHub · GitHub · GHSA-525V-9GP9-W22H

ID
GHSA-525V-9GP9-W22H
Date
Source
GitHub
Vendor
GitHub
Threat
medium
CVSS
5.9
EPSS
0.00204

Summary

### Summary The forge TLS client's check for a missing server certificate read the wrong property and never ran. A malicious TLS server, or an on-path attacker who removes the server's Certificate message, can make `connection.process()` throw a `TypeError`, which crashes applications that use the forge TLS client. Fixed in node-forge 1.4.1. ### Details After ServerHelloDone, `tls.handleServerHelloDone()` in…

Timeline

Published by source
2026-10-30

Risk context

  • Reported severity or threat level: medium.
  • Reported CVSS score: 5.9 out of 10.
  • Reported EPSS value: 0.00204.
  • Review exposure for the affected product or family: npm: node-forge.

Product

npm: node-forge

What to do

General, cautious steps (verify details in the official source):

  • Review exposure and plan remediation based on risk and environment.
  • Identify affected product versions in your inventory and verify whether you are impacted.
  • Apply vendor patches/updates or recommended mitigations as soon as available.
  • Read the official advisory for exact affected versions and remediation steps.

Official advisory

Evidence and provenance

Canonical advisory ID
GHSA-525V-9GP9-W22H
Source
GitHub
Vendor
GitHub
Published by source
2026-10-30
Last source activity
2026-10-30
Additional identifiers
CVE-2026-118778
Curated by
hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.