VulnerabilityPublished 19 Feb 2026Updated 2 Mar 2026

CVE-2026-1292: Tanium Trends · Sensitive Data in Logs

Affects Tanium TrendsSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.11.79 or 3.10.20 when convenient.

Data as of 26 Oct 2026, 10:12 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.11.79, 3.10.20

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 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 Trends to 3.11.79 or 3.10.20.

Affected software

Product	Affected	Fixed in
TaniumTrends	Affected >=3.11.0 <3.11.79	Fixed in 3.11.79
TaniumTrends	Affected >=3.10.0 <3.10.20	Fixed in 3.10.20

CPE configurations (2)

cpe:2.3:a:tanium:service_trends:3.10.19:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_trends:3.11.77:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-1292, organizations should: 1) Immediately apply any patches or updates released by Tanium addressing this vulnerability. 2) Review and harden access controls on log files to ensure only authorized personnel and processes can read sensitive logs. 3) Implement log management best practices such as encrypting log files at rest and in transit to prevent unauthorized access. 4) Audit existing logs for exposure of sensitive information and securely purge or redact sensitive entries where feasible. 5) Monitor network and system access logs for unusual access patterns that could indicate attempts to exploit this vulnerability. 6) Limit network exposure of Tanium Trends interfaces to trusted networks and use network segmentation to reduce attack surface. 7) Educate system administrators and security teams about the risks of sensitive data in logs and enforce strict operational security policies around log handling. These steps go beyond generic advice by focusing on log security and access controls specific to this vulnerability.

Description

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

Impact

The primary impact of CVE-2026-1292 is the potential unauthorized disclosure of sensitive information through log files. This can lead to confidentiality breaches, exposing sensitive operational or user data that could be leveraged for further attacks such as social engineering, privilege escalation, or lateral movement within networks. Although the vulnerability does not affect system integrity or availability, the exposure of sensitive data can damage organizational reputation, violate compliance requirements (e.g., GDPR, HIPAA), and result in financial penalties. Organizations with extensive use of Tanium Trends in security monitoring or endpoint management environments are particularly at risk, as logs often contain detailed operational data. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially if attackers gain access to log files through other means. The vulnerability's medium severity indicates that while it is not critical, it requires timely remediation to prevent potential data leakage.

References

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

Community reviews

Loading reviews…