CVE-2026-118778

Forge: TLS client crash when the server sends no certificate

Published Oct 29, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge's TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.

Analysis

AI-generated

Technical impact

The vulnerability is caused by a wrong null‑check in the node‑forge TLS client. When a server omits the Certificate message, the client dereferences a missing certificate, leading to an uncaught exception and a crash of the connection or the entire process. The result is an unplanned termination of the application, effectively a denial‑of‑service.

Affected Systems

The affected product is the node‑forge library (also known as forge) provided by Digital Bazaar. Any JavaScript or Node.js application that imports forge and uses forge.tls.createConnection() is vulnerable when running a version earlier than 1.4.1. The fix was released in version 1.4.1 and later.

Risk and Exploitability

The CVSS score of 5.9 classifies the risk as medium. No EPSS information is available and the vulnerability is not listed in the CISA KEV catalog, suggesting a lower exploitation probability in the wild. Based on the description, it is inferred that an attacker controlling a TLS server or acting as a man‑in‑the‑middle could omit the Certificate message, leading to the crash. Therefore the common threat is a network‑based denial‑of‑service that could disrupt services relying on node‑forge.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade node‑forge to version 1.4.1 or newer.
  • If an upgrade is not immediately possible, remove any use of forge.tls.createConnection() to servers that might not provide a certificate or switch to an alternative TLS library.
  • Add sanity checks in any custom code to verify that serverCertificate is defined before accessing its properties, mitigating the null‑dereference flaw.

Generated by OpenCVE AI on October 29, 2026 at 21:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-525v-9gp9-w22h Forge: TLS client crash when the server sends no certificate
History
Type Values Removed Values Added
CPEs cpe:2.3:a:digitalbazaar:forge:*:*:*:*:*:node.js:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Digitalbazaar
Digitalbazaar forge
Vendors & Products Digitalbazaar
Digitalbazaar forge
Type Values Removed Values Added
Description Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge's TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.
Title Forge: TLS client crash when the server sends no certificate
Weaknesses CWE-476
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 4:20 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Analyzed
Published
Oct 29, 2026, 7:17 PM
Modified
Nov 10, 2026, 7:24 PM
Severity
Moderate
Public date
Oct 29, 2026, 6:44 PM