VulnerabilityPublished 5 Feb 2026Updated 6 Feb 2026

CVE-2025-15328: Tanium Enforce · Link Following

Affects Tanium EnforceSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium : upgrade to 2.8.544 or 2.7.314 when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.8.544, 2.7.314

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Tanium Enforce to 2.8.544 or 2.7.314.

Affected software

Product	Affected	Fixed in
TaniumEnforce	Affected >=2.7.0 <2.7.314 >=2.8.0 <2.8.544	Fixed in 2.8.544 2.7.314

CPE configurations (2)

cpe:2.3:a:tanium:service_enforce:2.7.313:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_enforce:2.8.543:*:*:*:*:*:*:*

AI-suggested

1. 2. Restrict local user permissions on systems running Tanium Enforce to minimize the risk of unauthorized file access. 3. Implement strict access controls and monitoring on endpoints to detect unusual file access patterns or symbolic link manipulations. 4. Educate users about the risks of interacting with untrusted content or executing unexpected actions within Tanium Enforce. 5. Use application whitelisting and endpoint detection and response (EDR) tools to monitor and block suspicious activities related to file system access. 6. Conduct regular audits of Tanium Enforce configurations and logs to identify potential exploitation attempts. 7. Isolate critical systems running Tanium Enforce from less trusted network segments to reduce the attack surface. 8. Coordinate with Tanium support for guidance on secure configuration and best practices to mitigate link following vulnerabilities.

Description

Tanium addressed an improper link resolution before file access vulnerability in Enforce.

Impact

For European organizations, the primary impact of CVE-2025-15328 lies in the potential unauthorized disclosure of sensitive information managed by Tanium Enforce, such as compliance reports, configuration data, or endpoint security status. This could lead to exposure of confidential corporate or personal data, potentially violating GDPR and other data protection regulations. The requirement for local access and user interaction limits the threat to insider attacks or scenarios where an attacker has already compromised a user account or workstation. However, given Tanium Enforce’s role in security operations, any compromise could undermine trust in endpoint management and compliance monitoring. Organizations in regulated sectors such as finance, healthcare, and critical infrastructure may face increased risks due to the sensitivity of the data involved. The medium severity rating suggests that while the vulnerability is not critical, it should be addressed promptly to prevent escalation or lateral movement within networks.

References

security.tanium.com/TAN-2025-007 (opens in a new tab)

Community reviews

Loading reviews…