VulnerabilityPublished 19 Feb 2026Updated 2 Mar 2026

CVE-2026-2605: Tanium TanOS · Sensitive Data in Logs

Affects Tanium TanOSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.8.6.0150 : update Tanium TanOS when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.8.6.0150, 1.8.5.0282, 1.8.4.0249

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Tanium TanOS to 1.8.6.0150, 1.8.5.0282 or 1.8.4.0249.

Affected software

Product	Affected	Fixed in
TaniumTanOS	Affected >=1.8.6 <1.8.6.0150	Fixed in 1.8.6.0150
TaniumTanOS	Affected >=1.8.5 <1.8.5.0282	Fixed in 1.8.5.0282
TaniumTanOS	Affected >=1.8.4 <1.8.4.0249	Fixed in 1.8.4.0249

CPE configurations (3)

cpe:2.3:a:tanium:tanos:1.8.4.0249:*:*:*:*:*:*:*
cpe:2.3:a:tanium:tanos:1.8.5.0282:*:*:*:*:*:*:*
cpe:2.3:a:tanium:tanos:1.8.6.0150:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2605, organizations should first verify if they are running affected TanOS versions (1.8.4, 1.8.5, or 1.8.6) and prioritize upgrading to patched versions once available from Tanium. In the absence of immediate patches, restrict access to log files by enforcing strict file permissions and limiting access to only trusted administrators. Implement network segmentation and firewall rules to reduce exposure of TanOS management interfaces to untrusted networks. Monitor logs and system access patterns for unusual or unauthorized access attempts to detect potential exploitation early. Employ endpoint detection and response (EDR) tools to identify suspicious activities related to log file access. Review and harden logging configurations to minimize sensitive data inclusion in logs where feasible. Conduct regular security audits and vulnerability assessments focused on Tanium deployments. Engage with Tanium support for any available interim fixes or guidance. Finally, ensure that incident response plans include scenarios involving sensitive data leakage from management platforms.

Description

Tanium addressed an insertion of sensitive information into log file vulnerability in TanOS.

Impact

The primary impact of CVE-2026-2605 is the potential unauthorized disclosure of sensitive information contained within TanOS log files. This could include operational details, security configurations, or other confidential data that, if accessed by attackers, could facilitate further attacks or data breaches. While the vulnerability does not allow modification or disruption of system operations, the confidentiality breach can undermine organizational security postures and compliance with data protection regulations. Organizations relying on Tanium for endpoint security and management may face increased risk of information leakage, which could be leveraged in targeted attacks or espionage. The medium severity rating reflects that exploitation is not trivial but possible, especially in environments where attackers have some level of access. The absence of known exploits in the wild suggests limited current exploitation but does not preclude future attempts. The impact is particularly relevant for sectors with high-value data or critical infrastructure where Tanium is deployed.

References

security.tanium.com/TAN-2026-006 (opens in a new tab)

Community reviews

Loading reviews…