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

CVE-2025-15340: Tanium Comply · Incorrect Default Permissions

Affects Tanium ComplySource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 2.32.155 : update Tanium Comply 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 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.32.155, 2.29.124, 2.24.159

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 Comply to 2.32.155, 2.29.124 or 2.24.159.

Affected software

Product	Affected	Fixed in
TaniumComply	Affected >=2.24.0 <2.24.159 >=2.29.0 <2.29.124 >=2.32.0 <2.32.155	Fixed in 2.32.155 2.29.124 2.24.159

CPE configurations (3)

cpe:2.3:a:tanium:service_comply:2.24.158:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_comply:2.29.123:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_comply:2.32.154:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-15340, European organizations should first identify all instances of Tanium Comply running vulnerable versions (2.24.0, 2.29.0, 2.32.0). Immediate steps include reviewing and tightening permission configurations to ensure that only authorized users have high privileges. In the absence of patches, implement compensating controls such as network segmentation to limit access to Tanium Comply servers, enhanced monitoring and logging of administrative actions, and strict access control policies for privileged accounts. Regular audits of user permissions and role assignments can help detect and prevent privilege creep. Additionally, employing multi-factor authentication (MFA) for administrative access reduces the risk of credential compromise. Security teams should also conduct internal penetration testing and vulnerability assessments focused on Tanium Comply deployments to verify the effectiveness of mitigations.

Description

Tanium addressed an incorrect default permissions vulnerability in Comply.

Impact

For European organizations, this vulnerability poses a risk to the confidentiality and integrity of compliance and endpoint management data. Tanium Comply is often deployed in large enterprises and critical infrastructure sectors such as finance, healthcare, and government agencies, where compliance data is sensitive and tightly regulated under frameworks like GDPR. Unauthorized access due to incorrect default permissions could lead to exposure of sensitive compliance reports, misconfiguration of endpoint policies, or unauthorized data modification, potentially resulting in regulatory non-compliance, reputational damage, and operational risks. Although exploitation requires high privileges, insider threats or compromised administrative accounts could leverage this vulnerability to escalate their access or exfiltrate data. The absence of availability impact reduces the risk of service disruption but does not diminish the seriousness of data confidentiality breaches. Given the medium severity and the nature of the affected product, organizations should consider this vulnerability a significant risk in their compliance and endpoint security environments.

References

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

Community reviews

Loading reviews…