Skip to content
Fencer Intel
high 7.4

CVE-2026-121565 json

Tanium addressed an improper certificate validation vulnerability in multiple products

published 6d ago modified 3d ago also EUVD-2026-116547

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

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.

Patch / fix

  • Tanium TanOS 1.8.5.0326, 1.8.6.0193, 1.9.0.0089
  • Tanium Asset 1.33.334, 1.36.182, 1.39.164
  • Tanium Comply 2.32.275, 2.35.337, 2.37.347
  • Tanium Connect 5.29.272, 5.37.177, 5.47.135
  • Tanium Integrity Monitor 3.6.608, 3.7.383, 3.8.362
  • Tanium Health Check 1.13.653
  • Tanium Endpoint Configuration Toolset Solution 1.51.61, 1.59.51, 1.71.26
  • Tanium Patch 3.24.328, 3.28.346, 3.32.383
  • Tanium Performance 1.25.196
  • Tanium Reputation 6.6.150, 6.7.143, 6.8.167
  • Tanium Reveal 2.4.109, 2.5.166
  • Tanium Threat Response 4.9.480, 4.12.353, 4.17.333

Is CVE-2026-121565 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
3d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Tanium TanOS
  • Tanium Asset
  • Tanium Comply
  • Tanium Connect
  • Tanium Integrity Monitor
  • Tanium Health Check
  • Tanium Endpoint Configuration Toolset Solution
  • Tanium Patch
  • Tanium Performance
  • Tanium Reputation
  • Tanium Reveal
  • Tanium Threat Response
  • Tanium Provision Host

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.