CVE-2025-15329VulnerabilityPublished 5 Feb 2026Updated 6 Feb 2026

CVE-2025-15329: Tanium Threat Response · Insertion of Sensitive Information Into Sent Data

Affects Tanium Threat ResponseSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium · fixed in 4.9.297 : update Tanium Threat Response when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

4.9Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.9.297, 4.6.518, 4.5.250

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: 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 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 Threat Response to 4.9.297, 4.6.518 or 4.5.250.

Affected software

Product	Affected	Fixed in
TaniumThreat Response	Affected >=4.5.0 <4.5.250 >=4.6.0 <4.6.518 >=4.9.0 <4.9.297	Fixed in 4.9.297 4.6.518 4.5.250

CPE configurations (3)

cpe:2.3:a:tanium:service_threatresponse:4.5.249:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_threatresponse:4.6.517:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_threatresponse:4.9.296:*:*:*:*:*:*:*

AI-suggested

1. 2. Restrict administrative and privileged access to Tanium Threat Response to a minimal set of trusted personnel, implementing strong authentication mechanisms such as multi-factor authentication (MFA). 3. Monitor network traffic for unusual data transmissions from Tanium endpoints or servers, focusing on unexpected data flows that could indicate information leakage. 4. Conduct regular audits of privileged accounts and review logs for suspicious activities related to data access or export. 5. Employ network segmentation to isolate Tanium management infrastructure from broader enterprise networks, limiting exposure in case of compromise. 6. Integrate Tanium logs and alerts into centralized security information and event management (SIEM) systems to enhance detection capabilities. 7. Educate security teams about the vulnerability and ensure incident response plans include scenarios involving EDR data leakage. 8. Consider temporary compensating controls such as disabling non-essential data export features if feasible until patches are applied.

Description

Tanium addressed an information disclosure vulnerability in Threat Response.

Impact

For European organizations, the primary impact is the potential exposure of sensitive information managed or processed by Tanium Threat Response. This could include endpoint telemetry, security event data, or other confidential operational details. Such leakage could aid adversaries in reconnaissance, lateral movement, or targeted attacks, especially in sectors with high-value data such as finance, healthcare, energy, and government. Although the vulnerability requires high privileges, insider threats or compromised administrative accounts could exploit it. The lack of impact on integrity and availability reduces the risk of service disruption but does not diminish the confidentiality concerns. Given the increasing reliance on EDR tools for cybersecurity defense, any compromise of their data integrity or confidentiality undermines trust and operational security. European organizations must consider this vulnerability in their risk assessments and incident response planning, particularly those with critical infrastructure or regulatory obligations under GDPR and NIS Directive.

References

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

Community reviews

Loading reviews…