{"answers":{"affected":"2 open source packages ship an affected version, including @libp2p/peer-store.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86039 exists.","fix":"Upgrade @libp2p/peer-store to 12.0.24 or later.","what":"CVE-2026-86039 is a high-severity vulnerability in js-libp2p, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-86039 and fix it if it is affected.\n\nWhat it is: CVE-2026-86039 is a high-severity vulnerability in js-libp2p, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86039 exists.\n\nAffected packages and fixed versions:\n- @libp2p/peer-store (npm): affected from 8.0.0; fixed in 12.0.24\n- @libp2p/peer-store (npm): affected from 8.0.0; fixed in 12.0.24\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-86039/ (Markdown: https://insights.sbomify.com/CVE-2026-86039/index.md)","id":"CVE-2026-86039","markdown":"https://insights.sbomify.com/CVE-2026-86039/index.md","name":"CVE-2026-86039","record":{"aliases":["GHSA-vrf4-mx87-p53w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libp2p networking library","requires_auth":"none","summary":"Attackers can poison the peer store with malicious addresses for victim peers, causing routing manipulation and connection failures in libp2p applications.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"libp2p is a JavaScript implementation of the libp2p networking stack. From 8.0.0 until 12.0.24, @libp2p/peer-store in packages/peer-store/src/index.ts uses consumePeerRecord to verify a RecordEnvelope signature but does not require PeerRecord.peerId in the signed payload to equal the signer peer ID derived by RecordEnvelope.openAndCertify. The expectedPeer option checks only the envelope signer, and the gossipsub Peer Exchange path can provide the attacker's own peer ID as expectedPeer. An attacker can therefore sign a record with the attacker's key, place a victim peer ID and attacker-controlled multiaddrs in the payload, and have certified addresses stored for the victim. The poisoned addresses can cause address-book corruption, dial redirection or failure, routing manipulation, and reachability disruption, although the connection upgrade still verifies remote peer identity and prevents a complete identity takeover. The issue is fixed in version 12.0.24.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"libp2p: PeerStore accepts attacker-signed PeerRecords for a victim peer ID and stores certified attacker addresses","id":"CVE-2026-86039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"libp2p: Unbounded RPC decode + synchronous subscription processing in @libp2p/floodsub allows unauthenticated DoS","id":"CVE-2026-86040"},"packages":[{"ecosystem":"npm","fixed":["12.0.24"],"introduced":["8.0.0"],"last_affected":[],"package":"@libp2p/peer-store","purl":null,"source":"GHSA-vrf4-mx87-p53w"},{"ecosystem":"npm","fixed":["12.0.24"],"introduced":["8.0.0"],"last_affected":[],"package":"@libp2p/peer-store","purl":"pkg:npm/%40libp2p/peer-store","source":"GHSA-vrf4-mx87-p53w"}],"prev":{"headline":"libp2p: Gossipsub StrictSign accepts attacker-signed messages as a victim RSA peer ID","id":"CVE-2026-86038"},"products":["js-libp2p"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["libp2p"]},"summary":"Attackers can poison the peer store with malicious addresses for victim peers, causing routing manipulation and connection failures in libp2p applications.","url":"https://insights.sbomify.com/CVE-2026-86039/"}