Relay service interruption via stale queue accounting
Published May 7, 2026 · Updated May 7, 2026
Incorrect behavior order in Tor before 0.4.9.7 allows remote attackers to interrupt relay service through Conflux traffic. conflux_clear_ooo_q frees queued relay messages and clears the list without subtracting their allocations from total_ooo_q_bytes, leaving global memory accounting inflated. Exploitation requires remote attackers to induce out-of-order Conflux traffic and queue teardown; the reported consequence is limited to relay availability.
Summary
What happened
Incorrect behavior order in Tor before 0.4.9.7 allows remote attackers to interrupt relay service through Conflux traffic. conflux_clear_ooo_q frees queued relay messages and clears the list without subtracting their allocations from total_ooo_q_bytes, leaving global memory accounting inflated. Exploitation requires remote attackers to induce out-of-order Conflux traffic and queue teardown; the reported consequence is limited to relay availability.
The record
- CVE
- CVE-2026-44600
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- The Tor Project
- Product
- Tor
- Classifications
- CWE-696, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record 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.4.9.7
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.
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