Public vulnerability disclosure

CVE-2026-118778

Forge: TLS client crash when the server sends no certificate

publishedCWE-476

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.

Technical severity5.9 mediumCVSS 3.1 · CNA: GitHub_M
Published2026-10-29Source updated 2026-11-03
Collected2026-11-034 attributed sources

Fixes and workarounds

Fix

node-forge (npm): OSV reports a fixed version 1.4.1. Check the advisory for supported release branches.

Source: OSV GHSA-525v-9gp9-w22h

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
forge
digitalbazaar
< 1.4.1 (affected) CNA: GitHub_M
node-forge

node-forge
npm
≥ 0; < 1.4.1 (affected, semver); OSV events: introduced 0; fixed 1.4.1
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "fixed": "1.4.1"
  }
]

Other versions: unaffected
OSV GHSA-525v-9gp9-w22h

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.9
medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCNA: GitHub_M
3.1 / 5.9
medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide