CVE-2025-15313VulnerabilityPublished 9 Feb 2026

CVE-2025-15313: Tanium EUSS · Link Following

Affects Tanium EUSSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 1.18.28 or 1.17.41 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

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 1.18.28, 1.17.41

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 9 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 2026-10-26.

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 EUSS to 1.18.28 or 1.17.41.

Affected software

Product	Affected	Fixed in
TaniumTanium EUSS	Affected >=1.17.0 <1.17.41 >=1.18.0 <1.18.28	Fixed in 1.18.28 1.17.41

CPE configurations (2)

cpe:2.3:a:tanium:endpoint_euss:1.17.40:*:*:*:*:*:*:*
cpe:2.3:a:tanium:endpoint_euss:1.18.27:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-15313, European organizations should first verify their Tanium EUSS version and prioritize upgrading to a patched version once officially released by Tanium. If you cannot patch yet, organizations should enforce strict access controls limiting Tanium EUSS usage to trusted administrators and service accounts, minimizing the number of users with low privileges who can interact with the system. Implementing robust monitoring and alerting for unusual file deletion activities or changes in critical directories related to Tanium operations can help detect exploitation attempts early. Network segmentation and endpoint protection measures should be enhanced to reduce the risk of lateral movement by attackers who gain low-privilege access. Additionally, organizations should review and harden file system permissions to prevent unauthorized link manipulation and consider application whitelisting to restrict execution of unauthorized scripts or commands that could exploit this vulnerability. Engaging with Tanium support for guidance and timely patch deployment is essential. Finally, conducting internal audits and penetration testing focused on link resolution and file access controls can help identify and remediate related weaknesses.

Description

CVE-2025-15313 is a medium-severity vulnerability in Tanium EUSS versions 1.17.0 and 1.18.0 that allows an authenticated user with low privileges to cause improper link resolution before file access, leading to arbitrary file deletion. The flaw does not require user interaction and affects the integrity of the system by enabling deletion of files without proper authorization checks. There are no known exploits in the wild as of now. The vulnerability is local access only, requiring low privileges, which limits its exploitation scope but still poses a risk to organizations using affected Tanium EUSS versions. European organizations relying on Tanium for endpoint security and systems management should prioritize patching to prevent potential misuse. Countries with higher adoption of Tanium products and critical infrastructure sectors are more likely to be impacted.

Impact

For European organizations, the primary impact of CVE-2025-15313 lies in the potential unauthorized deletion of files by low-privileged authenticated users within Tanium EUSS environments. This can disrupt endpoint management operations, lead to loss of critical configuration or state files, and potentially degrade security monitoring and response capabilities. Organizations in sectors with stringent regulatory requirements for data integrity, such as finance, healthcare, and critical infrastructure, may face compliance risks if such file deletions affect audit logs or security controls. Although the vulnerability does not allow remote exploitation or direct data exfiltration, insider threats or compromised low-privilege accounts could leverage this flaw to sabotage systems or evade detection. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially in environments where Tanium EUSS is widely deployed. Disruption to endpoint security functions could indirectly increase exposure to other cyber threats. Therefore, European enterprises using affected Tanium versions should consider this vulnerability a moderate risk to operational integrity and security posture.

References

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

Community reviews

Loading reviews…