CVE-2026-44601
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:LSummary
CVE-2026-44601 is a low-severity Improper Enforcement of a Single, Unique Action (CWE-837) vulnerability in Torproject Tor. Its CVSS base score is 3.7 (Low).
Operationally, ranked at the 27th 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 AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-28302
Vulnerability Data
Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a double close of a circuit, aka TROVE-2026-009.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.3V6.5.1V7.6.2V17.3.1
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces approved authorizations for actions; when policy requires an action to occur only once, proper enforcement directly stops duplicate execution.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Authorization policy enforcement can include rules that restrict actions to a single use.
Logical access controls can incorporate mechanisms that block replay or repeated actions.
Preventing execution of unauthorized or duplicate actions directly addresses single-use enforcement.
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.
Access-control rules can enforce single-use or uniqueness constraints, but the control is broader than this specific weakness.
Managing access rights can include rules that limit an action to one occurrence, yet the control addresses rights in general.
Secure SDLC practices can require design controls for single-use actions, but the control addresses the entire lifecycle.
Application-security requirements can specify single-action enforcement, yet the control is wider in scope.
Secure-coding standards can mandate checks that prevent repeated actions, but the control covers many coding issues.
Information-access-restriction mechanisms can implement single-action limits, but the control covers broader access-restriction needs.