VulnerabilityPublished 5 Feb 2026Updated 6 Feb 2026

CVE-2025-15338: Tanium Partner Integration · Incorrect Default Permissions

Affects Tanium Partner IntegrationSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 1.3.40 : update Tanium Partner Integration when convenient.

Data as of 26 Oct 2026, 10:12 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.3.40, 1.2.33, 1.0.224

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 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 Partner Integration to 1.3.40, 1.2.33 or 1.0.224.

Affected software

Product	Affected	Fixed in
TaniumPartner Integration	Affected >=1.3.0 <1.3.40	Fixed in 1.3.40
TaniumPartner Integration	Affected >=1.2.0 <1.2.33	Fixed in 1.2.33
TaniumPartner Integration	Affected >=1.0.0 <1.0.224	Fixed in 1.0.224

CPE configurations (3)

cpe:2.3:a:tanium:service_partnerintegration:1.0.223:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_partnerintegration:1.2.32:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_partnerintegration:1.3.39:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-15338, European organizations should immediately audit the permission settings of Tanium Partner Integration components to identify and correct any overly permissive defaults. Restrict access to Partner Integration interfaces strictly to necessary personnel with validated high privileges and implement robust monitoring for unusual access patterns. In the interim, consider implementing network segmentation and access control lists (ACLs) to limit exposure of the Partner Integration service to trusted networks only. Additionally, conduct regular reviews of privileged accounts and enforce the principle of least privilege to reduce the risk of exploitation. Incorporating these steps into existing security operations and compliance frameworks will help mitigate potential exploitation risks effectively.

Description

Tanium addressed an incorrect default permissions vulnerability in Partner Integration.

Impact

For European organizations, the impact of CVE-2025-15338 can be significant, particularly for enterprises and critical infrastructure sectors relying on Tanium Partner Integration for endpoint management and security operations. Unauthorized access to sensitive data could lead to data breaches, intellectual property theft, or manipulation of security telemetry, undermining trust and operational integrity. The confidentiality and integrity impacts could affect compliance with GDPR and other data protection regulations, potentially resulting in legal and financial repercussions. Since the vulnerability requires high privileges, the risk is somewhat mitigated by existing access controls; however, insider threats or compromised privileged accounts could exploit this flaw. The absence of availability impact means operational disruption is unlikely, but the stealthy nature of data compromise increases detection difficulty. European organizations with extensive Tanium deployments should consider this vulnerability a priority to address to maintain security posture and regulatory compliance.

References

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

Community reviews

Loading reviews…