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

CVE-2025-15336: Tanium Performance · Incorrect Default Permissions

Affects Tanium PerformanceSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 1.22.288 : update Tanium Performance when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.22.288, 1.21.141, 1.17.134

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: 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 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-25.

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 Performance to 1.22.288, 1.21.141 or 1.17.134.

Affected software

Product	Affected	Fixed in
TaniumPerformance	Affected >=1.17.0 <1.17.134 >=1.21.0 <1.21.141 >=1.22.0 <1.22.288	Fixed in 1.22.288 1.21.141 1.17.134

CPE configurations (3)

cpe:2.3:a:tanium:service_performance:1.17.133:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_performance:1.21.140:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_performance:1.22.287:*:*:*:*:*:*:*

AI-suggested

1. Immediately verify if your organization uses Tanium Performance versions 1.17.0, 1.21.0, or 1.22.0 and prioritize these systems for review. 2. 3. Conduct a thorough audit of permission settings within Tanium Performance to ensure that default permissions have been corrected and adhere to the principle of least privilege. 4. Restrict administrative and high-privilege access to only trusted personnel and implement multi-factor authentication to reduce risk of privilege misuse. 5. Monitor logs and alerts for unusual access patterns or modifications to performance data that could indicate exploitation attempts. 6. Incorporate Tanium Performance into your organization's vulnerability management and incident response plans to ensure rapid detection and remediation of related threats. 7. Educate internal teams about the risks associated with elevated privileges and enforce strict access controls. 8. Consider network segmentation to limit the exposure of Tanium Performance servers to only necessary management networks.

Description

Tanium addressed an incorrect default permissions vulnerability in Performance.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality and integrity of endpoint performance data managed by Tanium Performance. Unauthorized access or modification of this data could lead to inaccurate monitoring, misinformed operational decisions, or exposure of sensitive system information. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, could face compliance risks if sensitive data is exposed. The requirement for high privileges to exploit the vulnerability reduces the likelihood of external attackers exploiting it directly but increases the risk from insider threats or attackers who have already gained elevated access. Disruption to monitoring capabilities could indirectly affect operational efficiency and incident response. Given Tanium's use in large enterprises and government agencies, the vulnerability could be leveraged for lateral movement or persistence within networks if combined with other attack vectors. The absence of known exploits in the wild provides a window for proactive mitigation, but organizations should not delay patching or permission audits.

References

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

Community reviews

Loading reviews…