Skip to main content
CVE-2026-1224VulnerabilityPublished Updated

CVE-2026-1224: Tanium Discover · Unthrottled Resource Allocation

Affects Tanium DiscoverSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium : upgrade to 4.15.130 or 4.10.134 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Tanium Discover to 4.15.130 or 4.10.134.

Affected software

ProductAffectedFixed in
TaniumDiscoverAffected
  • >=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

1. 2. Restrict network access to Tanium Discover management interfaces to trusted administrators only, using network segmentation and firewall rules. 3. Implement strict access controls and monitor for unusual administrative activity to prevent privilege escalation or misuse. 4. Monitor resource utilization metrics on servers running Tanium Discover to detect abnormal spikes that may indicate exploitation attempts. 5. Use rate limiting or traffic shaping at the network level to prevent excessive requests that could trigger resource exhaustion. 6. Conduct regular security audits and vulnerability assessments to ensure no other related weaknesses exist. 7. Develop incident response plans that include scenarios involving denial of service on critical management tools like Tanium Discover. 8. Educate privileged users on security best practices to reduce risk of credential compromise. These steps go beyond generic advice by focusing on network controls, monitoring, and administrative security tailored to the nature of this vulnerability.

Description

Tanium addressed an uncontrolled resource consumption vulnerability in Discover.

References

Community reviews

Loading reviews…