GHSA-WC36-XGCC-JWPR

GHSA-WC36-XGCC-JWPR is a high-severity security vulnerability in libp2p-core (rust), affecting versions >= 0.30.0-rc.1, < 0.30.2. It is fixed in 0.30.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Failure to verify the public key of a SignedEnvelope against the PeerId in a PeerRecord

Affected versions of this crate did not check that the public key the signature was created with matches the peer ID of the peer record.
Any combination was considered valid.

This allows an attacker to republish an existing PeerRecord with a different PeerId.

Impact

Affected versions

libp2p-core (>= 0.30.0-rc.1, < 0.30.2)

Security releases

libp2p-core → 0.30.2 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade libp2p-core to 0.30.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-WC36-XGCC-JWPR? GHSA-WC36-XGCC-JWPR is a high-severity security vulnerability in libp2p-core (rust), affecting versions >= 0.30.0-rc.1, < 0.30.2. It is fixed in 0.30.2.
  2. Which versions of libp2p-core are affected by GHSA-WC36-XGCC-JWPR? libp2p-core (rust) versions >= 0.30.0-rc.1, < 0.30.2 is affected.
  3. Is there a fix for GHSA-WC36-XGCC-JWPR? Yes. GHSA-WC36-XGCC-JWPR is fixed in 0.30.2. Upgrade to this version or later.
  4. Is GHSA-WC36-XGCC-JWPR exploitable, and should I be worried? Whether GHSA-WC36-XGCC-JWPR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-WC36-XGCC-JWPR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-WC36-XGCC-JWPR? Upgrade libp2p-core to 0.30.2 or later.

Other vulnerabilities in libp2p-core

Stop the waste.
Protect your environment with Kodem.