dbcve.org
DiscoverApplication · Tanium

CVE-2026-1224

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-26
Fix available
A fix is available. Upgrade to 4.10.134 / 4.15.130 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Tanium addressed an uncontrolled resource consumption vulnerability in Discover.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Tanium Discover contains an uncontrolled resource consumption vulnerability that could allow an authenticated attacker to exhaust system resources, potentially causing denial of service. The vulnerability is network-exploitable with medium severity (CVSS 6.5), likely stemming from insufficient validation or throttling of resource-intensive operations within the Discover module.

MitigationApply the vendor-supplied patch or update to a fixed Tanium version as specified in the security advisory. If immediate patching is not feasible, consider network segmentation and access controls to limit exposure to authenticated attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DiscoverApplication
Affected:>= 4.10.0, < 4.10.134>= 4.15, < 4.15.130

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Tanium Discover is installed
    Locate Tanium Discover installation directory or check Tanium console for Discover module presence
    Affected if Tanium Discover module is present in the environment
  2. Determine Tanium Discover version
    Access Tanium console or use Tanium CLI command to query Discover module version (e.g., 'taniumctl version' or console version information)
    Affected if Installed version matches CVE-2026-1224 affected ranges: >= 4.10.0 and < 4.10.134, OR >= 4.15 and < 4.15.130
  3. Confirm Discover module is active
    Check Tanium console or configuration to verify the Discover module is enabled and running
    Affected if Discover module is enabled and processing scans or sensor data
  4. Review resource consumption logs
    Examine Tanium server logs and system monitoring for unusual resource usage patterns related to Discover scan operations
    Affected if Excessive CPU, memory, or disk I/O is observed from Discover processes
  5. Check for unauthorized or high-volume Discover scans
    Review Discover scan history and scheduled scan configurations for abnormal frequency or scope
    Affected if An unusually high volume of scans is observed from a single authenticated user session

Environment is affected if Tanium Discover is installed with a version between 4.10.0 and 4.10.133, or between 4.15 and 4.15.129, and the Discover module is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.10.134 / 4.15.130 or later
Fixed in 4.10.1344.15.130
Interim mitigation

Apply the vendor-supplied patch or update to a fixed Tanium version as specified in the security advisory. If immediate patching is not feasible, consider network segmentation and access controls to limit exposure to authenticated attackers.

Recommended fix High confidence

Upgrade to Discover version 4.10.134 or later (for 4.10.x branch), or 4.15.130 or later (for 4.15.x branch)

  1. 1. Identify the current Tanium Discover version by accessing the Tanium Console and navigating to the Discover module.
  2. 2. If running version >= 4.10.0 and < 4.10.134, plan upgrade to version 4.10.134 or later.
  3. 3. If running version >= 4.15 and < 4.15.130, plan upgrade to version 4.15.130 or later.
  4. 4. Review Tanium upgrade documentation and ensure backup of current configuration.
  5. 5. Perform upgrade following standard Tanium upgrade procedures for the Discover module.
  6. 6. Verify the upgrade was successful and Discover module functions normally.
  7. 7. Confirm the installed version matches the target fixed release.
Caveat Standard Tanium upgrade considerations apply; review release notes for any module-specific changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Discover Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1224 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data