Skip to main content
VulnerabilityPublished

CVE-2026-86865: Tanium Asset · SQL Injection

Affects Tanium AssetSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High · fixed in 1.39.153 : patch Tanium Asset soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.39.153, 1.36.174, 1.33.326
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Tanium Asset to 1.39.153, 1.36.174 or 1.33.326.

Affected software

ProductAffectedFixed in
TaniumAssetAffected
  • >=1.39 <1.39.153
Fixed in
  • 1.39.153
TaniumAssetAffected
  • >=1.36 <1.36.174
Fixed in
  • 1.36.174
TaniumAssetAffected
  • >=1.33 <1.33.326
Fixed in
  • 1.33.326

AI-suggested

A fix is available. Users should upgrade Tanium Asset to versions 1.33.326, 1.36.174, 1.39.153 or later to remediate this SQL injection vulnerability.

Description

CVE-2026-86865 is a high-severity SQL injection vulnerability in Tanium Asset. It allows improper neutralization of special elements in SQL commands, potentially leading to full compromise of confidentiality, integrity, and availability. The vulnerability affects specific versions prior to fixed releases. Tanium has addressed this issue in later versions.

References

Community reviews

Loading reviews…