CVE-2026-0925VulnerabilityPublished 26 Jan 2026Updated 2 Feb 2026

CVE-2026-0925: Tanium Discover · Improper Validation of Specified Quantity in Input

Affects Tanium DiscoverSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low : upgrade to 4.15.130 or 4.10.134 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

2.7Low

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.15.130, 4.10.134

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jan 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-26.

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.15.130 or 4.10.134.

Affected software

Product	Affected	Fixed in
TaniumDiscover	Affected >=4.10 <4.10.134 >=4.15 <4.15.130	Fixed in 4.15.130 4.10.134

CPE configurations (2)

cpe:2.3:a:tanium:service_asset:4.10.133:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_asset:4.15.129:*:*:*:*:*:*:*

AI-suggested

2) Restrict high-privilege access to Tanium Discover to only trusted and trained personnel, minimizing the risk of malicious or accidental exploitation. 3) Implement strict input validation and monitoring on the network level to detect anomalous requests targeting Tanium Discover interfaces. 4) Regularly audit user privileges and session activities to identify any suspicious behavior from privileged accounts. 5) Employ network segmentation to isolate Tanium Discover servers from less trusted network zones, reducing exposure. 6) Maintain up-to-date backups and incident response plans to quickly recover from potential service disruptions. 7) Monitor vendor advisories and threat intelligence feeds for any emerging exploit information related to this vulnerability.

Description

Tanium addressed an improper input validation vulnerability in Discover.

Impact

For European organizations, the primary impact of CVE-2026-0925 is a potential denial of service affecting the availability of Tanium Discover services. This could disrupt asset discovery and management operations, potentially delaying incident response and IT operations workflows. Since Tanium Discover is often deployed in enterprise and critical infrastructure environments, any downtime could affect operational efficiency and security monitoring capabilities. However, the impact on confidentiality and integrity is negligible, and exploitation requires authenticated users with high privileges, limiting the attack surface. The absence of known exploits reduces immediate risk, but organizations should remain vigilant. Disruptions could be more consequential in sectors relying heavily on continuous asset visibility, such as finance, healthcare, and government agencies within Europe.

References

security.tanium.com/TAN-2026-002 (opens in a new tab)

Community reviews

Loading reviews…