Security Resilience

CVE-2026-44597

Torproject Tor ≤ 0.4.9.7

Published
07 May 2026
Modified
17 June 2026
Patch / advisory
View 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.0063 49th percentile
Risk Priority 34 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-44597 is a low-severity Incorrect Provision of Specified Functionality (CWE-684) vulnerability in Torproject Tor. Its CVSS base score is 3.7 (Low).

Operationally, ranked at the 49th 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 SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in its payload, aka TROVE-2026-011.

CWE(s)
CWE-684

Related Threats

CVEs Like This One

CVE-2026-44603Same product: Torproject Tor
CVE-2026-44602Same product: Torproject Tor
CVE-2026-44601Same product: Torproject Tor
CVE-2026-44599Same product: Torproject Tor
CVE-2026-77584Same product: Torproject Tor
CVE-2026-77641Same product: Torproject Tor
CVE-2026-77638Same product: Torproject Tor
CVE-2026-44600Same product: Torproject Tor
CVE-2026-77642Same product: Torproject Tor
CVE-2023-23589Same product: Torproject Tor

Affected Assets

torproject
tor
≤ 0.4.9.7

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities are performed precisely to discover when delivered functionality fails to match published specifications.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and supporting tools reduces the chance that specified functionality will be implemented incorrectly.

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 Secure development life cycle partial match
blocks

A.8.25 requires that security be designed and implemented in the SDLC (including secure coding, requirements, testing and checkpoints), but does not itself stop incorrect functionality from being exploitable once the code is written and deployed; the weakness can still be present and reachable.

A.8.26 Application security requirements partial match
blocks

Explicit application security requirements and acceptance criteria help ensure the delivered software matches its intended specifications.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development and acceptance validates that implemented functionality conforms to specifications before release.

A.8.32 Change management partial match
blocks

Change management processes reduce the chance of unintended functional deviations during updates, though they do not directly address initial specification conformance.

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-684, a class-level weakness, and none of its children carries one either.

References