Peer address poisoning via mismatched signed identity
Published Sep 17, 2026 · Updated Sep 21, 2026
Authenticity validation failure in @libp2p/peer-store 8.0.0 through 12.0.23 allows remote attackers to poison certified peer addresses. consumePeerRecord verifies the envelope signature but stores addresses under the untrusted payload peer ID without requiring it to match the signer. Applications that consume untrusted signed peer records can redirect or fail later dials, but connection identity verification prevents full peer impersonation.
Summary
What happened
Authenticity validation failure in @libp2p/peer-store 8.0.0 through 12.0.23 allows remote attackers to poison certified peer addresses. consumePeerRecord verifies the envelope signature but stores addresses under the untrusted payload peer ID without requiring it to match the signer. Applications that consume untrusted signed peer records can redirect or fail later dials, but connection identity verification prevents full peer impersonation.
The record
- CVE
- CVE-2026-86039
- Published
- Sep 17, 2026
- Updated
- Sep 21, 2026
- Vendor
- libp2p
- Product
- js-libp2p
- Classifications
- CWE-345, CWE-290
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 8.0.0, < 12.0.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Certified peer-record address hijack TypeScript proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started