HTTP service interruption via unbounded response queues
Published Feb 14, 2025 · Updated Feb 18, 2025
Resource exhaustion in Monero 0.18.3.4 and earlier allows remote attackers to interrupt HTTP services via concurrent connections. The Epee HTTP server tracks neither queued response bytes nor per-address and global connection counts, allowing unread responses and connections to consume resources without effective bounds. The affected HTTP endpoint must be reachable; exhaustion can terminate connections and deny daemon or wallet RPC availability without compromising data.
Summary
What happened
Resource exhaustion in Monero 0.18.3.4 and earlier allows remote attackers to interrupt HTTP services via concurrent connections. The Epee HTTP server tracks neither queued response bytes nor per-address and global connection counts, allowing unread responses and connections to consume resources without effective bounds. The affected HTTP endpoint must be reachable; exhaustion can terminate connections and deny daemon or wallet RPC availability without compromising data.
The record
- CVE
- CVE-2025-26819
- Published
- Feb 14, 2025
- Updated
- Feb 18, 2025
- Vendor
- Monero Project
- Product
- Monero
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 18, 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 <ec74ff4a3d3ca38b7912af680209a45fd1701c3d
What conditions does exploitation require?
What is affected?
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