Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4487-j8r4-4g2f

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

CVSS 3.7 LowEPSS 0.0017 · 6th percentile

Published by the GitHub Advisory Database at 30 Oct 2026, 23:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
node-forgenpm<1.4.11.4.1
Identifiers
GHSA-4487-j8r4-4g2f · CVE-2026-118780
Weakness (CWE)
CWE-295 · CWE-471
Tags
Published
30 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of the npm package node-forge before 1.4.1 are affected. When a CA store created by pki.createCaStore() holds two or more certificates with the same subject name, pki.verifyCertificateChain() permanently removes those certificates from the store. A remote, unauthenticated peer can trigger this by sending a certificate that names that shared subject as its issuer, after which later verifications against those CA certificates fail until the store is recreated. Upgrade to node-forge 1.4.1, which fixes the issue; until then, pass a fresh CA store per verification or per connection.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
3.7 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 6th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 29 Oct 2026, 18:47 UTC Confirmed by the CVE List
  2. 29 Oct 2026, 19:17 UTC Confirmed by NVD
  3. 31 Oct 2026, 13:32 UTC First seen by agentprime
  4. 31 Oct 2026, 13:32 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.