CVE-2025-15339VulnerabilityPublished 5 Feb 2026

CVE-2025-15339: Tanium Discover · Incorrect Default Permissions

Affects Tanium DiscoverSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.10.118 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 4.10.118

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 Discover to 4.10.118.

Affected software

Product	Affected	Fixed in
TaniumDiscover	Affected >=4.10.0 <4.10.118	Fixed in 4.10.118

CPE configurations (1)

cpe:2.3:a:tanium:service_discover:4.10.117:*:*:*:*:*:*:*

AI-suggested

European organizations should take the following specific actions: 1) Immediately audit Tanium Discover 4.10.0 deployments to identify and review default permission settings, ensuring that only necessary privileges are granted to users and roles. 3) Implement strict access controls and role-based access management to limit high privilege accounts and monitor their usage closely. 4) Use network segmentation to restrict access to Tanium Discover components to trusted administrators and systems only. 5) Enable detailed logging and monitoring of Tanium Discover activities to detect unauthorized access or changes promptly. 6) Conduct regular security assessments and penetration tests focusing on privilege escalation and permission misconfigurations. 7) Educate administrators about the risks of default permissions and enforce configuration hardening best practices. These steps go beyond generic advice by focusing on permission audits, access control tightening, and proactive monitoring tailored to Tanium Discover environments.

Description

Tanium addressed an incorrect default permissions vulnerability in Discover.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to confidentiality and integrity of sensitive data managed by Tanium Discover. Enterprises relying on Tanium for asset management and endpoint visibility could face unauthorized data exposure or manipulation if an attacker with high privileges exploits the incorrect permissions. This could lead to data breaches, compliance violations (e.g., GDPR), and operational disruptions in asset tracking. Since availability is not impacted, service continuity is less of a concern. However, the requirement for high privileges means that the vulnerability is more likely to be exploited as part of a multi-stage attack where initial access has already been obtained. Organizations in critical sectors such as finance, energy, healthcare, and government are particularly at risk due to the sensitive nature of the data managed by Tanium Discover. The lack of known exploits reduces immediate threat but does not eliminate the risk, especially as attackers often target misconfigurations to escalate privileges or move laterally within networks.

References

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

Community reviews

Loading reviews…