VulnerabilityPublished 19 Feb 2026Updated 2 Mar 2026

CVE-2026-2435: Tanium Asset · SQL Injection

Affects Tanium AssetSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium · fixed in 1.36.108 : update Tanium Asset when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.36.108, 1.33.269, 1.32.179

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 Asset to 1.36.108, 1.33.269 or 1.32.179.

Affected software

Product	Affected	Fixed in
TaniumAsset	Affected >=1.36 <1.36.108	Fixed in 1.36.108
TaniumAsset	Affected >=1.33 <1.33.269	Fixed in 1.33.269
TaniumAsset	Affected >=1.32 <1.32.179	Fixed in 1.32.179

CPE configurations (3)

cpe:2.3:a:tanium:service_asset:1.32.178:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_asset:1.33.268:*:*:*:*:*:*:*
cpe:2.3:a:tanium:service_asset:1.36.107:*:*:*:*:*:*:*

AI-suggested

Organizations should promptly apply the security patches released by Tanium for versions 1.32, 1.33, and 1.36 of Tanium Asset. If you cannot patch yet, restrict access to the Tanium Asset interface to trusted users only and enforce the principle of least privilege to limit the capabilities of authenticated users. Conduct thorough audits of user permissions to ensure no unnecessary privileges are granted. Implement monitoring and alerting for anomalous SQL queries or unusual database activity related to Tanium Asset. Deploy web application firewalls (WAFs) or database activity monitoring tools capable of detecting and blocking SQL injection attempts. Additionally, review and harden network segmentation to isolate Tanium Asset servers from less trusted network zones. Educate administrators and users about the risks of SQL injection and the importance of secure coding and input validation practices. Regularly update and test incident response plans to quickly address any potential exploitation attempts.

Description

Tanium addressed a SQL injection vulnerability in Asset.

Impact

The vulnerability could allow an authenticated low-privilege user to execute arbitrary SQL commands, potentially leading to unauthorized data disclosure, data modification, or partial denial of service within the Tanium Asset database. This could compromise the confidentiality and integrity of asset information, which is critical for security operations and compliance reporting. The availability impact is likely limited but could disrupt asset management functions temporarily. Organizations relying on Tanium Asset for endpoint visibility and security posture assessment may experience degraded security monitoring effectiveness, increasing the risk of undetected threats. While no exploits are currently known in the wild, the presence of this vulnerability increases the attack surface and could be leveraged in targeted attacks, especially in environments with weak internal access controls. The requirement for authenticated access reduces the risk from external attackers but does not eliminate insider threats or lateral movement scenarios.

References

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

Community reviews

Loading reviews…