{"items":[{"id":"NVI-00008888","kind":"vulnerability","title":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","revision":6,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-4487-j8r4-4g2f","CVE-2026-118780"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-105d9ab6f8b6a77c96b020403e88902b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:15.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d"},{"kind":"CVSS","as_of":"2026-10-30T17:07:53.700Z","value":"3.7 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-55732afdba304b2d68c107b580505558"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.172%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.0665. Missing scores are unknown.","source_id":"sr-105d9ab6f8b6a77c96b020403e88902b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-909be70021cf54798c01a92e6bfbe056","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T23:13:55.657Z"},{"id":"sr-55732afdba304b2d68c107b580505558","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118780","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-118780","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-105d9ab6f8b6a77c96b020403e88902b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118780","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.317Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-07T14:02:01.397Z","source_updated_at":"2026-10-30T23:02:15.000Z","source_disclosed_at":"2026-10-30T23:02:14.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008888","kind":"vulnerability","title":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-4487-j8r4-4g2f","CVE-2026-118780"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0d4c3f96b2126fed28dd4e84d59df71d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:15.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d"},{"kind":"CVSS","as_of":"2026-10-30T17:07:53.700Z","value":"3.7 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-55732afdba304b2d68c107b580505558"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.172%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.06581. Missing scores are unknown.","source_id":"sr-0d4c3f96b2126fed28dd4e84d59df71d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-909be70021cf54798c01a92e6bfbe056","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T23:13:55.657Z"},{"id":"sr-55732afdba304b2d68c107b580505558","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118780","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-118780","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-0d4c3f96b2126fed28dd4e84d59df71d","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118780","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.845Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-05T19:10:23.273Z","source_updated_at":"2026-10-30T23:02:15.000Z","source_disclosed_at":"2026-10-30T23:02:14.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008888","kind":"vulnerability","title":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4487-j8r4-4g2f","CVE-2026-118780"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0d4c3f96b2126fed28dd4e84d59df71d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:15.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.172%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.06581. Missing scores are unknown.","source_id":"sr-0d4c3f96b2126fed28dd4e84d59df71d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-909be70021cf54798c01a92e6bfbe056","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T23:13:55.657Z"},{"id":"sr-0d4c3f96b2126fed28dd4e84d59df71d","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118780","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.845Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-04T10:04:47.590Z","source_updated_at":"2026-10-30T23:02:15.000Z","source_disclosed_at":"2026-10-30T23:02:14.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008888","kind":"vulnerability","title":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4487-j8r4-4g2f","CVE-2026-118780"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-a1a2590db4cdd3ca2af6ff873f0c5310"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:15.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.172%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.06586. Missing scores are unknown.","source_id":"sr-a1a2590db4cdd3ca2af6ff873f0c5310"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-909be70021cf54798c01a92e6bfbe056","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T23:13:55.657Z"},{"id":"sr-a1a2590db4cdd3ca2af6ff873f0c5310","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118780","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.375Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-04T02:53:03.180Z","source_updated_at":"2026-10-30T23:02:15.000Z","source_disclosed_at":"2026-10-30T23:02:14.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008888","kind":"vulnerability","title":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4487-j8r4-4g2f","CVE-2026-118780"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:15.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-909be70021cf54798c01a92e6bfbe056","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T23:13:55.657Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-909be70021cf54798c01a92e6bfbe056"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-01T01:03:56.582Z","source_updated_at":"2026-10-30T23:02:15.000Z","source_disclosed_at":"2026-10-30T23:02:14.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008888","kind":"vulnerability","title":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4487-j8r4-4g2f","CVE-2026-118780"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:15.000Z","value":"3.7 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1cf1ecc0a4ceadf114c130cf79d70e6d","url":"https://github.com/advisories/GHSA-4487-j8r4-4g2f","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4487-j8r4-4g2f","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1cf1ecc0a4ceadf114c130cf79d70e6d"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nWhen 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 while trying each one as the issuer. A peer can send any certificate that names that subject as its issuer to make all later verifications against those CA certificates fail. Fixed in node-forge 1.4.1.\n\n### Details\n\n`pki.verifyCertificateChain()` (`lib/x509.js`) asks the CA store for the issuer of each certificate with `caStore.getIssuer()`. When the store holds several certificates with the same subject, `caStore.getIssuer()` returns the store's own internal array of those certificates (`caStore.certs[hash]`, built by `addCertificate()`). `verifyCertificateChain()` used that array directly as its list of candidate parents and called `parents.shift()` on it while trying each candidate. Every candidate it tried, including the one that finally verified the certificate, was removed from the store.\n\nOnce the array is empty, `getIssuer()` returns an empty list, no candidate is tried, and verification fails with \"Certificate signature is invalid.\" `hasCertificate()` and `listAllCertifi","public_affected_ranges":["<= 1.4.0"]}],"null_published_at":"2026-10-31T22:13:27.121Z","source_updated_at":"2026-10-30T23:02:15.000Z","source_disclosed_at":"2026-10-30T23:02:14.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:55:49.621Z"}],"next_cursor":null,"snapshot_revision":"42594"}