Public vulnerability disclosure

CVE-2026-118780

Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store

publishedCWE-295CWE-471

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pki.verifyCertificateChain(), pki.createCaStore(), duplicate subject names to process the relevant input or security decision. node-forge modified the CA store while trying certificates that shared a subject name during pki.verifyCertificateChain(). A failed chain verification could permanently remove trusted CA certificates from the store, causing later valid chains to fail and creating a persistent availability impact for applications that reused the store. This issue is fixed in version 1.4.1.

Technical severity3.7 lowCVSS 3.1 · CNA: GitHub_M
Published2026-10-29Source updated 2026-11-04
Collected2026-11-043 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-4487-j8r4-4g2f

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-4487-j8r4-4g2f

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 / 3.7
low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LCNA: GitHub_M

Exploit evidence

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