CVE-2026-44600
Torproject Tor ≤ 0.4.9.7
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-44600 is a low-severity Incorrect Behavior Order (CWE-696) vulnerability in Torproject Tor. Its CVSS base score is 3.7 (Low).
Operationally, ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and RA-5 (Vulnerability Monitoring and Scanning) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-28237
Vulnerability Data
Tor before 0.4.9.7 mishandles accounting of the conflux out-of-order queue during the clearing of a queue, aka TROVE-2026-010.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages can discover incorrect ordering of related behaviors before deployment.
Vulnerability scanning may surface order-related weaknesses after code is built but does not address their root cause.
Mandating a documented development process and standards enforces review of behavior ordering within the software lifecycle.
Security and privacy engineering principles applied during design and implementation directly require correct sequencing of operations to avoid introducing order-dependent flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates security in the SDLC including secure coding, requirements, checkpoints, testing and developer training that can catch and stop incorrect behavior ordering before it reaches production, but this is only a minority slice of the weakness class (most instances arise from implementation errors not governed by process mandates).
Secure system architecture and engineering principles require proper ordering of design and implementation steps.
Secure coding standards enforce correct execution order of security-critical operations.
Security testing can detect ordering flaws but does not prevent them during development.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-696, a class-level weakness, and none of its children carries one either.