CVE-2022-24759: `@chainsafe/libp2p-noise` contains TypeScript implementation of noise protocol, an encryption protocol used in

Q: How do I fix CVE-2022-24759?

js-libp2p-noise: upgrade to 4.1.2, 5.0.3. Exact commands for each OS are on this page.

Q: Is CVE-2022-24759 being exploited?

CVE-2022-24759 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-24759 affect?

CVE-2022-24759 affects js-libp2p-noise. Severity is high (CVSS 8.1). `@chainsafe/libp2p-noise` contains TypeScript implementation of noise protocol, an encryption protocol used in libp2p. `@chainsafe/libp2p-noise` before 4.1.2 and 5.0.3 does not correctly validate signatures during the handshake process. Thi

Routine

HIGH 8.1UPGRADE

CVE-2022-24759 is a high-severity flaw (CVSS 8.1) affecting js-libp2p-noise. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

`@chainsafe/libp2p-noise` contains TypeScript implementation of noise protocol, an encryption protocol used in libp2p. `@chainsafe/libp2p-noise` before 4.1.2 and 5.0.3 does not correctly validate signatures during the handshake process. This may allow a man-in-the-middle to pose as other peers and get those peers banned. Users should upgrade to version 4.1.2 or 5.0.3 to receive a patch. There are currently no known workarounds.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Weakness	CWE-347
Published	2022-03-17
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: chainsafe

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-03-17 17:15 UTCPublished CVE record published
2026-06-17 04:32 UTCUpdated Record last modified

chainsafe js-libp2p-noise UPGRADE

Affected: < 4.1.2 · >= 5.0.0 and < 5.0.3

Fixed in: 4.1.2, 5.0.3

Safe to downgrade to: a release before 5.0.0

1. Check installed version

npm ls js-libp2p-noise

2. UPGRADE to 4.1.2

npm install js-libp2p-noise@">=4.1.2"

3. If no update is available yet, DOWNGRADE to a release before 5.0.0

npm view js-libp2p-noise versions npm install js-libp2p-noise@"<5.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-24759?

js-libp2p-noise: upgrade to 4.1.2, 5.0.3. Exact commands for each OS are on this page.

Is CVE-2022-24759 being exploited?

CVE-2022-24759 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-24759 affect?

CVE-2022-24759 affects js-libp2p-noise. Severity is high (CVSS 8.1). `@chainsafe/libp2p-noise` contains TypeScript implementation of noise protocol, an encryption protocol used in libp2p. `@chainsafe/libp2p-noise` before 4.1.2 and 5.0.3 does not correctly validate signatures during the handshake process. Thi

How urgent is CVE-2022-24759?

Priority 39/100. High severity

References

← Back to latest CVEs