CVE-2026-110789

7.5High

Published 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.5CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on availability
Weakness
CWE-130, CWE-400

What an attacker gets

Unauthenticated remote attackers can cause a denial of service by stalling the event loop and exhausting memory. This is triggered by sending a crafted public key during the Identify handshake.

Root cause

The ASN.1 DER decoder in @libp2p/crypto enters an infinite synchronous loop when processing maliciously large element lengths in a public key.

Affected versions

@libp2p/crypto versions prior to 5.1.22

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Fix & remediation

Upgrade @libp2p/crypto to version 5.1.22 or later. If you cannot patch immediately, restrict incoming peer connections via firewall rules to known trusted nodes.

remediation — bash
$ npm install @libp2p/crypto@5.1.22

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 5.1.22, the @libp2p/crypto code reached by the default Identify service accepts a remote peer’s crafted publicKey before peer-id or signature verification and passes it through publicKeyFromProtobuf to the ASN.1 DER decoder. readLength in packages/crypto/src/keys/rsa/der.ts accepts long-form element lengths larger than the remaining buffer, causing readInteger and related readers to loop synchronously over an attacker-claimed length from a very small key blob. Because decoding occurs in one event-loop tick before the remotePeer equality check in packages/protocol-identify/src/identify.ts, the Identify timeout cannot interrupt it, allowing repeated unauthenticated connections to stall all timers and peers and transiently exhaust memory. This issue is fixed in version 5.1.22.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-110789