{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-118780 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-118780 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-118780 is a low-severity vulnerability in digitalbazaar forge, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-118780 and fix it if it is affected.\n\nWhat it is: CVE-2026-118780 is a low-severity vulnerability in digitalbazaar forge, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-118780 in the wild and no public exploit code.\n\nAffected product: digitalbazaar forge. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-118780/ (Markdown: https://insights.sbomify.com/CVE-2026-118780/index.md)","id":"CVE-2026-118780","markdown":"https://insights.sbomify.com/CVE-2026-118780/index.md","name":"CVE-2026-118780","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-471","name":"Modification of Assumed-Immutable Data (MAID)"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store","id":"CVE-2026-118780","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript.","id":"CVE-2026-118781"},"packages":[],"prev":{"headline":"Forge: Regular expression denial of service in PEM decoding (pem.decode)","id":"CVE-2026-118779"},"products":["forge"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["digitalbazaar"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-118780/"}