Tanium addressed an improper certificate validation vulnerability in multiple products
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.5.0326, 1.8.6.0193, 1.9.0.0089, 1.33.334, 1.36.182, and 33 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.5.0326, 1.8.6.0193, 1.9.0.0089, 1.33.334, 1.36.182, or one of 33 more.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.4/10CVSS 7.4
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
CVE-2026-121565 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.4 (high) and affects TanOS, Asset, Comply and 10 more; fixed in 1.8.5.0326, 1.8.6.0193, 1.9.0.0089 and 35 more.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 1.8.5.0326, 1.8.6.0193, 1.9.0.0089, 1.33.334, 1.36.182, and 33 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Tanium's products, which are used for endpoint management and security, are affected by a flaw in how they check digital certificates. Because the software could trust certificates signed by intermediate authorities whose private keys were compromised, an attacker could potentially impersonate trusted services.
Read the original description
Tanium addressed an improper certificate validation vulnerability in multiple products. Products have been updated to distrust several intermediate CA certificates associated with compromised private keys.
What to do
Upgrade to a fixed version: 1.8.5.0326, 1.8.6.0193, 1.9.0.0089, 1.33.334, 1.36.182, or one of 33 more.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Tanium TanOS
From 1.8.5 · fixed in 1.8.5.0326; From 1.8.6 · fixed in 1.8.6.0193; From 1.9.0 · fixed in 1.9.0.0089
- Tanium Asset
From 1.33 · fixed in 1.33.334; From 1.36 · fixed in 1.36.182; From 1.39 · fixed in 1.39.164
- Tanium Comply
From 2.32 · fixed in 2.32.275; From 2.35 · fixed in 2.35.337; From 2.37 · fixed in 2.37.347
- Tanium Connect
From 5.29 · fixed in 5.29.272; From 5.37 · fixed in 5.37.177; From 5.47 · fixed in 5.47.135
- Tanium Integrity Monitor
From 3.6 · fixed in 3.6.608; From 3.7 · fixed in 3.7.383; From 3.8 · fixed in 3.8.362
- Tanium Health Check
From 1.13 · fixed in 1.13.653
- Tanium Endpoint Configuration Toolset Solution
From 1.51 · fixed in 1.51.61; From 1.59 · fixed in 1.59.51; From 1.71 · fixed in 1.71.26
- Tanium Patch
From 3.24 · fixed in 3.24.328; From 3.28 · fixed in 3.28.346; From 3.32 · fixed in 3.32.383
Show all 13 packagesShow fewer packages
- Tanium Performance
From 1.22 · fixed in 1.22.355; From 1.23 · fixed in 1.23.318; From 1.25 · fixed in 1.25.196
- Tanium Reputation
From 6.6 · fixed in 6.6.150; From 6.7 · fixed in 6.7.143; From 6.8 · fixed in 6.8.167
- Tanium Reveal
From 2.4 · fixed in 2.4.109; From 2.5 · fixed in 2.5.166
- Tanium Threat Response
From 4.9 · fixed in 4.9.480; From 4.12 · fixed in 4.12.353; From 4.17 · fixed in 4.17.333
- Tanium Provision Host
From 10.4.100 · fixed in 10.4.100; From 10.8.115 · fixed in 10.8.115; From 10.9.113 · fixed in 10.9.113; From 10.10.189 · fixed in 10.10.189; From 10.11.127 · fixed in 10.11.127
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121565
Is CVE-2026-121565 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Tanium's products do not properly validate certificates, so a connection can be trusted when it should not be. Successful abuse could give access to data the user should not be able to read or change.Source: security.tanium.com
Which versions are affected by CVE-2026-121565?
TanOS: from 1.8.5 before 1.8.5.0326; from 1.8.6 before 1.8.6.0193; from 1.9.0 before 1.9.0.0089. Asset: from 1.33 before 1.33.334; from 1.36 before 1.36.182; from 1.39 before 1.39.164. Comply: from 2.32 before 2.32.275; from 2.35 before 2.35.337; from 2.37 before 2.37.347. Connect: from 5.29 before 5.29.272; from 5.37 before 5.37.177; from 5.47 before 5.47.135. Integrity Monitor: from 3.6 before 3.6.608; from 3.7 before 3.7.383; from 3.8 before 3.8.362. 8 more packages are listed on the page.Source: cve.now feed data
Am I affected, and how do I check?
Affected builds are Tanium TanOS before 1.8.5.0326, 1.8.6.0193 and 1.9.0.0089, and many Tanium products before their listed fixed builds, including Asset, Comply, Connect, Patch and Provision Host. Check the installed product version against the fixed build for your release line, for example Asset before 1.33.334, 1.36.182 or 1.39.164. Provision Host 10.4 is affected before 10.4.100.Source: security.tanium.com
How do I fix CVE-2026-121565?
Upgrade each affected Tanium product to the fixed build for its release line listed in the advisory. Provision Host and cx-stream tools should be updated to the listed fixed builds as well.Source: security.tanium.com