CVE-2025-15330
Improper Input Validation in Tanium Deploy Risks Data Integrity
Publication date: 2026-02-05
Last updated on: 2026-02-10
Assigner: Tanium
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tanium | deploy | From 2.26.0 (inc) to 2.26.1279 (exc) |
| tanium | deploy | From 2.30.0 (inc) to 2.30.175 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-15330 is a high-severity vulnerability in Tanium Deploy caused by improper input validation.'}, {'type': 'paragraph', 'content': "This flaw allows an authenticated Tanium user who has 'Deploy Deployment - Write' and 'Deploy Software Package - Write' permissions to execute unauthorized code on all endpoints within the Deploy context."}] [1]
How can this vulnerability impact me? :
The vulnerability can severely impact the confidentiality, integrity, and availability of your systems.
- Confidentiality: Unauthorized code execution could lead to data exposure.
- Integrity: Attackers could alter or corrupt data or system configurations.
- Availability: The vulnerability could be exploited to disrupt system operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There is no specific information provided about detection methods or commands to identify this vulnerability on your network or system.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update Tanium Deploy to a fixed version at or above v2.26.1279 (2024H2 Update 14) or v2.30.175 (Update 3 for 7.4 and 7.5 releases).
There are no available workarounds or mitigations other than applying the update.