VulnerabilityPublished 5 Feb 2026

CVE-2025-15321: Tanium Appliance · Untrusted Search Path

Affects Tanium ApplianceSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low · fixed in 1.8.5.0227 : update Tanium Appliance when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

2.7Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.8.5.0227, 1.8.5.0199, 1.8.3.0196

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 or the CVSS exploit maturity 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 Appliance to 1.8.5.0227, 1.8.5.0199 or 1.8.3.0196.

Affected software

Product	Affected	Fixed in
TaniumTanium Appliance	Affected >=1.8.5.0 <1.8.5.0227	Fixed in 1.8.5.0227
TaniumTanium Appliance	Affected >=1.8.5.0 <1.8.5.0199	Fixed in 1.8.5.0199
TaniumTanium Appliance	Affected >=1.8.3.0 <1.8.3.0196	Fixed in 1.8.3.0196

CPE configurations (3)

cpe:2.3:a:tanium:tanos:1.8.3.0195:*:*:*:*:*:*:*
cpe:2.3:a:tanium:tanos:1.8.5.0198:*:*:*:*:*:*:*
cpe:2.3:a:tanium:tanos:1.8.5.0226:*:*:*:*:*:*:*

AI-suggested

2) Restrict and monitor privileged user access to the Tanium Appliance to prevent unauthorized manipulation of the search path. 3) Implement strict file system permissions and integrity monitoring on directories involved in executable and library search paths to detect unauthorized changes. 4) Conduct regular audits of the appliance configuration and environment variables that influence search paths to ensure they do not include untrusted locations. 5) Employ application whitelisting and code signing where possible to prevent execution of unauthorized binaries. 6) Use network segmentation and access controls to limit exposure of the appliance to only trusted management networks. 7) Monitor logs and alerts for suspicious activity related to executable loading or privilege misuse within the appliance environment. These steps go beyond generic advice by focusing on controlling the attack surface related to search path manipulation and privileged access management specific to Tanium Appliance deployments.

Description

Tanium addressed an improper input validation vulnerability in Tanium Appliance.

Impact

For European organizations, the impact of CVE-2025-15321 is limited but non-negligible. Since exploitation requires high privileges, the vulnerability primarily poses a risk if an attacker has already compromised an account with elevated access. In such cases, the attacker could leverage the untrusted search path to execute malicious code within the appliance context, potentially leading to unauthorized disclosure of sensitive data managed by Tanium. This could affect confidentiality of endpoint management data or security telemetry. However, the vulnerability does not allow privilege escalation or denial of service directly, reducing its overall threat level. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, should be particularly cautious. The presence of this vulnerability could also be leveraged as part of a multi-stage attack chain. Given the appliance’s role in enterprise security operations, any compromise could undermine trust in endpoint security posture. Therefore, European enterprises using Tanium Appliance should assess their exposure and implement mitigations promptly to maintain compliance with data protection regulations like GDPR.

References

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

Community reviews

Loading reviews…