VulnerabilityPublished 5 Feb 2026

CVE-2025-15333: Tanium Threat Response · Incorrect Default Permissions

Affects Tanium Threat ResponseSource CVE Database V5

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.9.324, 4.6.536, 4.5.266

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 Threat Response to 4.9.324, 4.6.536 or 4.5.266.

Affected software

Product	Affected	Fixed in
TaniumThreat Response	Affected >=4.9.0 <4.9.324	Fixed in 4.9.324
TaniumThreat Response	Affected >=4.6.0 <4.6.536	Fixed in 4.6.536
TaniumThreat Response	Affected >=4.5.0 <4.5.266	Fixed in 4.5.266

CPE configurations (3)

cpe:2.3:a:tanium:service_threatresponse:4.5.265:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_threatresponse:4.6.535:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_threatresponse:4.9.323:*:*:*:*:*:*:*

AI-suggested

Immediately audit and review the default permissions configured in Tanium Threat Response installations, focusing on user roles and access controls to ensure least privilege principles are enforced.
3. Restrict network access to the Tanium Threat Response management interfaces to trusted administrators only, using network segmentation and firewall rules. 4. Implement strong authentication mechanisms and monitor privileged account usage for unusual activity. 5. Conduct regular security assessments and penetration tests to verify that no unauthorized information disclosure is possible. 6. Educate security teams about the vulnerability and ensure incident response plans include steps to handle potential information leakage scenarios. 7. If immediate patching is not possible, consider temporary compensating controls such as disabling affected features or limiting user access until remediation is complete.

Description

Tanium addressed an information disclosure vulnerability in Threat Response.

Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive information collected or managed by Tanium Threat Response. Since the product is often deployed in enterprise environments for endpoint security and incident response, exposure of such data could aid attackers in reconnaissance or lateral movement within networks. The impact is primarily on confidentiality, with no direct effect on system integrity or availability. However, leaked information could include details about endpoints, security events, or configurations that adversaries might exploit. Organizations in sectors with high regulatory requirements for data protection, such as finance, healthcare, and critical infrastructure, could face compliance risks if sensitive data is exposed. The medium severity rating suggests that while the risk is not critical, it is significant enough to warrant timely remediation to prevent potential escalation or exploitation. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially if attackers develop techniques to leverage this vulnerability.

References

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

Community reviews

Loading reviews…