{"id":"CVE-2026-118780","kind":"vulnerability","aliases":["CVE-2026-118780"],"related":[],"title":"node-forge: failed chain check can permanently drop trusted CA certificates","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 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.","summary":"node-forge, a JavaScript TLS and crypto library, modifies its CA store when certificates share a subject name during chain verification. A failed verification can permanently remove trusted CAs, so later valid chains fail, which breaks availability for apps that reuse the store.","severity":"low","cvss":3.7,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["javascript","node-forge","package","tls"],"not_affected_if":["fresh-store-per-check","no-chain-verification"],"how_to_check":"- Find `node-forge` in `package-lock.json`, `yarn.lock` or `pnpm-lock.yaml` and read the resolved version.\n- Check whether the app calls `pki.createCaStore()` and reuses that store across requests.\n- Run `npm ls node-forge` to see every copy in the dependency tree.","fix":"- `node-forge` `1.4.1`","status":"open","published_at":"2026-10-29T19:17:20+00:00","first_seen_at":"2026-10-29T19:26:47+00:00","triaged_at":"2026-10-29T19:27:33+00:00","updated_at":"2026-10-29T19:27:33+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-29T19:27:33Z","model":"claude-haiku-5-5","output":{"fix":"- `node-forge` `1.4.1`","reach":"network","title":"node-forge: failed chain check can permanently drop trusted CA certificates","impact":"low","summary":"node-forge, a JavaScript TLS and crypto library, modifies its CA store when certificates share a subject name during chain verification. A failed verification can permanently remove trusted CAs, so later valid chains fail, which breaks availability for apps that reuse the store.","audience":"developers","category":"package","nicknames":[],"who_cares":["node-forge","javascript","tls"],"confidence":0.7,"fix_status":"available","needs_auth":"unknown","worst_case":"trusted CA certificates are removed, breaking later chain validation","analyst_note":"","how_to_check":"- Find `node-forge` in `package-lock.json`, `yarn.lock` or `pnpm-lock.yaml` and read the resolved version.\n- Check whether the app calls `pki.createCaStore()` and reuses that store across requests.\n- Run `npm ls node-forge` to see every copy in the dependency tree.","plain_action":"","needs_analyst":false,"not_affected_if":["no-chain-verification","fresh-store-per-check"],"who_is_affected":"Applications that use node-forge's pki.verifyCertificateChain() with a CA store created by pki.createCaStore() and reuse that store across verifications are exposed. Code that does not verify certificate chains with node-forge, or that creates a fresh store per check, is unlikely to be affected. Teams that only use node-forge for unrelated crypto can skip it.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"low"},"cost_usd":0.000711,"input_tokens":4222,"output_tokens":577,"severity_before":"low"},"analyst_status":null,"analyst_note":null,"search":"'-118780':15A,18A '-2026':14A,17A '1.4.1':87C,159C 'affect':89C 'also':70C 'app':64B 'applic':148C 'avail':62B,145C 'break':61B 'ca':11A,36B,110C,130C 'call':71C 'cas':54B 'caus':135C 'certif':12A,39B,114C,131C 'chain':5A,45B,58B,124C,138C 'check':6A 'could':126C 'creat':142C 'crypto':32B 'cve':13A,16A 'decis':104C 'drop':9A 'duplic':94C 'fail':4A,48B,59B,123C,140C 'fix':156C 'forg':3A,22B,27B,69C,74C,107C 'impact':146C 'implement':78C,90C 'input':101C 'issu':154C 'javascript':19B,29B,84C 'later':56B,136C 'layer':81C 'librari':33B 'modifi':34B,108C 'name':43B,96C,119C 'nativ':77C 'node':2A,21B,26B,73C,106C 'node-forg':1A,20B,25B,72C,105C 'packag':23B 'perman':8A,51B,127C 'persist':144C 'pki.createcastore':93C 'pki.verifycertificatechain':92C,121C 'prior':85C 'process':98C 'relev':100C 'remov':52B,128C 'reus':66B,150C 'secur':82C,103C 'share':40B,116C 'store':37B,68B,111C,134C,152C 'subject':42B,95C,118C 'tls':24B,30B 'transport':80C 'tri':113C 'trust':10A,53B,129C 'use':91C 'valid':57B,137C 'verif':46B,49B,125C 'version':158C","nicknames":[],"mitigations":[],"who_affected":"Applications that use node-forge's pki.verifyCertificateChain() with a CA store created by pki.createCaStore() and reuse that store across verifications are exposed. Code that does not verify certificate chains with node-forge, or that creates a fresh store per check, is unlikely to be affected. Teams that only use node-forge for unrelated crypto can skip it.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"developers","plain_action":null,"first_public_at":"2026-10-29T19:17:20+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","cvss_by":"security-advisories@github.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-118780","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118780","severity":null,"published_at":"2026-10-29T19:17:20+00:00","modified_at":"2026-10-29T19:17:20+00:00","first_seen_at":"2026-10-29T19:26:47+00:00","fetched_at":"2026-10-29T19:26:47+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}