CVE-2025-15331
Tanium Connect 5.22.0 – 5.22.100
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2025-15331 is a medium-severity Incomplete Cleanup (CWE-459) vulnerability in Tanium Connect. Its CVSS base score is 4.3 (Medium).
Operationally, ranked at the 24th 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 SC-6 (Resource Availability) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-206837
Vulnerability Data
Tanium addressed an uncontrolled resource consumption vulnerability in Connect.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly limits resource consumption caused by incomplete cleanup (CWE-459) in Tanium Connect before exhaustion occurs.
Provides denial-of-service protections that mitigate the uncontrolled resource consumption vulnerability in Tanium Connect.
Enables monitoring of system resources to identify anomalous consumption stemming from the Tanium Connect flaw.
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.
Secure-development practices and coding standards normally require proper resource release and cleanup.
Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.
Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.
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.
Explicitly requires secure deletion of temporary or residual data, directly addressing incomplete cleanup.
SDLC practices include cleanup steps, yet the weakness can still occur if those steps are omitted.
Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.
Change-management processes may require cleanup verification, but the control itself does not address the weakness.