CVE-2026-2350VulnerabilityPublished 19 Feb 2026Updated 2 Mar 2026

CVE-2026-2350: Tanium Interact · Sensitive Data in Logs

Affects Tanium InteractSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.5.102 or 3.2.196 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.102, 3.2.196, 4.1.257

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

Attack Vector: Network
Attack Complexity: Low
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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 2026-10-25.

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 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 Interact to 3.5.102 or 3.2.196; TDS to 4.1.257.

Affected software

Product	Affected	Fixed in
TaniumInteract	Affected >=3.2.0 <3.2.196 >=3.5.0 <3.5.102	Fixed in 3.5.102 3.2.196
TaniumTDS	Affected >=4.1.0 <4.1.257	Fixed in 4.1.257

CPE configurations (3)

cpe:2.3:a:tanium:service_interact:3.2.195:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_interact:3.5.101:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_tds:4.1.256:*:*:*:*:*:*:*

AI-suggested

1. 2. Restrict access to log files containing sensitive information by implementing strict file permissions and access controls, ensuring only authorized personnel and systems can read them. 3. Implement network segmentation and firewall rules to limit network access to Tanium Interact management interfaces and logging systems, reducing exposure to potential attackers. 4. Enable and monitor audit logging for access to log files to detect unauthorized attempts to read sensitive information. 5. Review and sanitize logging configurations to minimize logging of sensitive data where possible, following the principle of least privilege and data minimization. 6. Conduct regular security assessments and penetration testing focused on log file security and access controls within the Tanium environment. 7. Educate security and IT teams on the risks associated with sensitive data exposure in logs and best practices for secure log management. 8. Consider deploying additional security controls such as encryption for log files at rest and in transit to protect sensitive information from unauthorized access.

Description

Tanium addressed an insertion of sensitive information into log file vulnerability in Interact and TDS.

Impact

The primary impact of CVE-2026-2350 is the unauthorized disclosure of sensitive information through log files. This can lead to significant confidentiality breaches, including exposure of credentials, session tokens, or other sensitive operational data. Such exposure can facilitate further attacks such as privilege escalation, lateral movement, or data exfiltration within an organization's network. Since Tanium Interact is used for endpoint management and security operations, compromised sensitive data could undermine an organization's security posture and incident response capabilities. The vulnerability does not affect system integrity or availability directly, but the confidentiality breach alone can have severe consequences, especially in regulated industries or organizations handling sensitive data. The medium severity rating reflects a balance between the ease of exploitation and the impact scope. Organizations worldwide relying on Tanium Interact for endpoint security are at risk, particularly those with remote or network-exposed management consoles. The absence of known exploits reduces immediate risk but does not eliminate the potential for future exploitation.

References

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

Community reviews

Loading reviews…