CVE
Tanium TanOS sensitive data exposure in log files
Affects TanOS systems recently restored from a backup, where an attacker can access the Backup Restore Log or an Appliance and Platform Files support bundle. Fixed in 1.8.5.0333.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.5.0333, 1.8.6.0209, 1.9.0.0113
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The TanOS system has recently been restored from a backup. The attacker has access to the Backup Restore Log or an "Appliance and Platform Files" support bundle (TSG).
Summary
Tanium addressed an insertion of sensitive information into a log file vulnerability in TanOS.
Who should check
Teams running Tanium TanOS appliances on 2025H1 before Update 28, 2025H2 before Update 18, or 2026H1 before Update 11, especially those that restored from backup.
“TanOS prior to Update 28 (v1.8.5 to v1.8.5.0333)”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The TanOS system has recently been restored from a backup. The attacker has access to the Backup Restore Log or an "Appliance and Platform Files" support bundle (TSG).Upgrade to a fixed version: 1.8.5.0333, 1.8.6.0209, 1.9.0.0113.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131575 (Tanium addressed an insertion of sensitive information into a log file vulnerability in TanOS.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131575 (entry last updated 2026-11-18):
Affected:
- Tanium TanOS: from 1.8.5, fixed in 1.8.5.0333; from 1.8.6, fixed in 1.8.6.0209; from 1.9.0, fixed in 1.9.0.0113
Fixed versions: 1.8.5.0333, 1.8.6.0209, 1.9.0.0113.
Conditions (all must be true for the bug to be hit):
- The TanOS system has recently been restored from a backup. (source: https://security.tanium.com/TAN-2026-120)
- The attacker has access to the Backup Restore Log or an "Appliance and Platform Files" support bundle (TSG). (source: https://security.tanium.com/TAN-2026-120)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131575 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131575 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://security.tanium.com/TAN-2026-120
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131575
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131575"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Tanium TanOS
From 1.8.5 · fixed in 1.8.5.0333; From 1.8.6 · fixed in 1.8.6.0209; From 1.9.0 · fixed in 1.9.0.0113
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | security.tanium.com · TAN-2026-120 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131575 |
| Record | NVD · CVE-2026-131575 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-131575
Is CVE-2026-131575 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?
TanOS writes sensitive information into a log file. An attacker who can read the Backup Restore Log or an Appliance and Platform Files support bundle can use it to gain access to a TanOS system that has recently been restored from a backup.Source: security.tanium.com
Which versions are affected by CVE-2026-131575?
TanOS: from 1.8.5 before 1.8.5.0333; from 1.8.6 before 1.8.6.0209; from 1.9.0 before 1.9.0.0113.Source: cve.now feed data
Am I affected, and how do I check?
The affected ranges are TanOS 1.8.5 before 1.8.5.0333, 1.8.6 before 1.8.6.0209, and 1.9.0 before 1.9.0.0113. The exposure applies only to a system recently restored from a backup, so check the TanOS version against these ranges and whether a restore has happened recently.Source: security.tanium.com
How do I fix CVE-2026-131575?
Update TanOS to 1.8.5.0333 (Update 28) or later on the 1.8.5 branch, or to 1.8.6.0209 or 1.9.0.0113 on those branches.Source: security.tanium.com