Security Resilience

CVE-2026-44601

Torproject Tor ≤ 0.4.9.7

Published
07 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0060 48th percentile
Risk Priority 33 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

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, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 48th 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

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

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1012 Query Registry Discovery
Adversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-44603Same product: Torproject Tor
CVE-2026-77584Same product: Torproject Tor
CVE-2026-77642Same product: Torproject Tor
CVE-2026-77641Same product: Torproject Tor
CVE-2026-44602Same product: Torproject Tor
CVE-2026-44599Same product: Torproject Tor
CVE-2026-44597Same product: Torproject Tor
CVE-2026-77638Same product: Torproject Tor
CVE-2026-44600Same product: Torproject Tor
CVE-2023-6759Shared CWE-837

Affected Assets

torproject
tor
≤ 0.4.9.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.3.3
  • V6.5.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.

PR.AA-05 partial match
blocks

Authorization policy enforcement can include rules that restrict actions to a single use.

PR.IR-01 partial match
blocks

Logical access controls can incorporate mechanisms that block replay or repeated actions.

PR.PS-05 partial match
blocks

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.

degrades

Access-control rules can enforce single-use or uniqueness constraints, but the control is broader than this specific weakness.

degrades

Managing access rights can include rules that limit an action to one occurrence, yet the control addresses rights in general.

blocks

Secure SDLC practices can require design controls for single-use actions, but the control addresses the entire lifecycle.

blocks

Application-security requirements can specify single-action enforcement, yet the control is wider in scope.

prevents

Secure-coding standards can mandate checks that prevent repeated actions, but the control covers many coding issues.

References