What is GHSA-RCH7-F4H5-X9RJ?

GHSA-RCH7-F4H5-X9RJ is a critical-severity security vulnerability in libp2p-secio (npm), affecting versions < 0.9.0. It is fixed in 0.9.0.

How severe is GHSA-RCH7-F4H5-X9RJ?

GHSA-RCH7-F4H5-X9RJ has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of libp2p-secio are affected by GHSA-RCH7-F4H5-X9RJ?

libp2p-secio (npm) versions < 0.9.0 is affected.

Is there a fix for GHSA-RCH7-F4H5-X9RJ?

Yes. GHSA-RCH7-F4H5-X9RJ is fixed in 0.9.0. Upgrade to this version or later.

Is GHSA-RCH7-F4H5-X9RJ exploitable, and should I be worried?

Whether GHSA-RCH7-F4H5-X9RJ 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.

What actually determines whether GHSA-RCH7-F4H5-X9RJ 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.

How do I fix GHSA-RCH7-F4H5-X9RJ?

Upgrade libp2p-secio to 0.9.0 or later.

GHSA-RCH7-F4H5-X9RJ in libp2p-secio

Q: How severe is GHSA-RCH7-F4H5-X9RJ?

GHSA-RCH7-F4H5-X9RJ has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of libp2p-secio are affected by GHSA-RCH7-F4H5-X9RJ?

libp2p-secio (npm) versions < 0.9.0 is affected.

Q: Is there a fix for GHSA-RCH7-F4H5-X9RJ?

Yes. GHSA-RCH7-F4H5-X9RJ is fixed in 0.9.0. Upgrade to this version or later.

Q: Is GHSA-RCH7-F4H5-X9RJ exploitable, and should I be worried?

Whether GHSA-RCH7-F4H5-X9RJ 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.

Q: What actually determines whether GHSA-RCH7-F4H5-X9RJ 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.

Q: How do I fix GHSA-RCH7-F4H5-X9RJ?

Upgrade libp2p-secio to 0.9.0 or later.

Summary

Identity Spoofing in libp2p-secio

Affected versions of libp2p-secio does not correctly verify that the PeerId of DstPeer matches the PeerId discovered in the crypto handshake, resulting in a high severity identity spoofing vulnerability.

Impact

GHSA-RCH7-F4H5-X9RJ has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.9.0); upgrading removes the vulnerable code path.

Affected versions

libp2p-secio (< 0.9.0)

Security releases

libp2p-secio → 0.9.0 (npm)

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 environment New to Kodem? Get a demo →

Remediation advice

Update to version 0.9.0 or later.

Frequently Asked Questions

What is GHSA-RCH7-F4H5-X9RJ? GHSA-RCH7-F4H5-X9RJ is a critical-severity security vulnerability in libp2p-secio (npm), affecting versions < 0.9.0. It is fixed in 0.9.0.
How severe is GHSA-RCH7-F4H5-X9RJ? GHSA-RCH7-F4H5-X9RJ has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of libp2p-secio are affected by GHSA-RCH7-F4H5-X9RJ? libp2p-secio (npm) versions < 0.9.0 is affected.
Is there a fix for GHSA-RCH7-F4H5-X9RJ? Yes. GHSA-RCH7-F4H5-X9RJ is fixed in 0.9.0. Upgrade to this version or later.
Is GHSA-RCH7-F4H5-X9RJ exploitable, and should I be worried? Whether GHSA-RCH7-F4H5-X9RJ 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
What actually determines whether GHSA-RCH7-F4H5-X9RJ 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.
How do I fix GHSA-RCH7-F4H5-X9RJ? Upgrade libp2p-secio to 0.9.0 or later.