Cyber Resilience

CVE-2025-15324

Tanium Engage 1.3.0 – 1.3.37

Published
05 February 2026
Modified
10 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H
EPSS Score 0.0015 5th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-15324 is a medium-severity Link Following (CWE-59) vulnerability in Tanium Engage. Its CVSS base score is 6.6 (Medium).

Operationally, ranked at the 5th 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-5 (System Documentation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Tanium addressed a documentation issue in Engage.

CWE(s)
CWE-59

Related Threats

CVEs Like This One

CVE-2025-15310Same vendor: Tanium
CVE-2025-15313Same vendor: Tanium
CVE-2025-15319Same vendor: Tanium
CVE-2025-15314Same vendor: Tanium
CVE-2025-15318Same vendor: Tanium
CVE-2025-15333Same vendor: Tanium
CVE-2025-15336Same vendor: Tanium
CVE-2026-2605Same vendor: Tanium
CVE-2025-15316Same vendor: Tanium
CVE-2025-15331Same vendor: Tanium

Affected Assets

tanium
engage
1.3.0 — 1.3.37 · 1.6.0 — 1.6.193

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SA-5 System Documentation
  • AC-3 Access Enforcement
  • CM-6 Configuration Settings
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2

Mitigating Controls (NIST 800-53 r5) AI

SA-5 System Documentation good match
prevent

Directly addresses the root cause by requiring complete, accurate system documentation that would have prevented the CWE-59 link-following exposure in Tanium Engage.

AC-3 Access Enforcement partial match
prevent

Enforces access decisions on file resources, limiting the ability of an attacker to exploit improper symbolic-link resolution before the documentation flaw was corrected.

CM-6 Configuration Settings partial match
prevent

Mandates secure configuration settings that can disable or restrict unsafe link-following behavior in the absence of proper vendor documentation.

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.PS-06 mostly match
prevents

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

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.29 Security testing in development and acceptance mostly match
detects

Security testing can detect link-following flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include input validation and safe file-access design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

A.8.3 Information access restriction none match
none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References