Skip to main content
Public proof of conceptFix availableAwaiting NVD analysis

CVE-2026-86038

A public proof of concept exists; no exploitation attested.

  • Published2026-09-17
  • Fixed in16.0.5
  • WeaknessCWE-345 · CWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

libp2p is a JavaScript implementation of the libp2p networking stack. From 15.0.0 until 16.0.5, @libp2p/gossipsub uses the default StrictSign policy in packages/gossipsub/src/utils/buildRawMessage.ts, where validateToRawMessage verifies a signature with attacker-controlled msg.key but skips binding that key to msg.from when the claimed author is an RSA peer ID that does not inline a public key. An unauthenticated attacker can place a victim RSA peer ID in msg.from, sign the message with the attacker's private key, and supply the attacker's public key in msg.key, causing the message to be accepted and propagated as authored by the victim. Applications that trust message.from for validators, authorization, accounting, moderation, reputation, or audit logging can process attacker-controlled data under false origin attribution. The issue is fixed in version 16.0.5.

Timeline

dates in UTC
  1. 2026-09-1716:18CVE publishedNVD

Versions per branch

OSV
@libp2p/gossipsub
BranchAffectedFixed in
16.0≥ 15.0.0, < 16.0.516.0.5

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • libp2p js-libp2p
    Affected
    • = >= 15.0.0, < 16.0.5no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-17

Fix

  1. Update @libp2p/gossipsub to 16.0.5

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2026-09-17
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-345, CWE-347known since 2026-10-23
  • FIRST EPSSEPSS score0.2 %2026-11-16
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2026-09-17

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2026-09-17
Last Modified
2026-09-30
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-c3gv-825q-fvmp

Frequently asked questions

What is CVE-2026-86038?

libp2p is a JavaScript implementation of the libp2p networking stack. From 15.0.0 until 16.0.5, @libp2p/gossipsub uses the default StrictSign policy in packages/gossipsub/src/utils/buildRawMessage.ts, where validateToRawMessage verifies a signature with attacker-controlled msg.key but skips binding that key to msg.from when the claimed author is an RSA peer ID that does not inline a public key. An unauthenticated attacker can place a victim RSA peer ID in msg.from, sign the message with the attacker's private key, and supply the attacker's public key in msg.key, causing the message to be accepted and propagated as authored by the victim. Applications that trust message.from for validators, authorization, accounting, moderation, reputation, or audit logging can process attacker-controlled data under false origin attribution. The issue is fixed in version 16.0.5.

Is CVE-2026-86038 actively exploited?

A proof-of-concept exploit exists for CVE-2026-86038, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-86038?

CVE-2026-86038 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running @libp2p/gossipsub? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record