CVE-2025-15344
SQL Injection Vulnerability in Tanium Asset Component
Publication date: 2026-01-29
Last updated on: 2026-03-09
Assigner: Tanium
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tanium | asset | to 1.28.254 (exc) |
| tanium | asset | From 1.32 (inc) to 1.32.161 (exc) |
| tanium | asset | From 1.33 (inc) to 1.33.250 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15344 is a medium-severity SQL injection vulnerability in the Tanium Asset service. It affects authenticated users who have the 'Asset API - Write' permission, allowing them to manipulate SQL queries executed by the Asset service. This could enable an attacker to interfere with the database queries, potentially leading to unauthorized data access or modification. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with certain permissions to manipulate SQL queries in the Tanium Asset service, which may lead to unauthorized access, modification, or disruption of data. The impact on confidentiality, integrity, and availability is considered low, but it still poses a risk of data compromise or service disruption. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Tanium Asset service to the fixed versions: for 2024H1 Release, update to Update 27 (v1.28.254) or later; for 2024H2 Release, update to Update 16 (v1.32.161) or later; and for 2025H1 Release, update to Update 10 (v1.33.250) or later. No other workarounds or mitigations are provided. [1]