Node service interruption via unbounded RSA keys
Published Jul 14, 2025 · Updated Jul 14, 2025
Resource exhaustion in libp2p py-libp2p before 0.2.3 allows remote authenticated users to interrupt a node via a large RSA key. RSAPublicKey.from_bytes imports an unbounded peer-supplied key, and subsequent signature verification consumes excessive processing time. A connected peer must supply the oversized key; confidentiality and integrity remain unaffected, while node availability is reduced.
Summary
What happened
Resource exhaustion in libp2p py-libp2p before 0.2.3 allows remote authenticated users to interrupt a node via a large RSA key. RSAPublicKey.from_bytes imports an unbounded peer-supplied key, and subsequent signature verification consumes excessive processing time. A connected peer must supply the oversized key; confidentiality and integrity remain unaffected, while node availability is reduced.
The record
- CVE
- CVE-2025-29606
- Published
- Jul 14, 2025
- Updated
- Jul 14, 2025
- Vendor
- libp2p
- Product
- py-libp2p
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2025CVE publishedPublication date reported by the CVE source.
- Jul 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo