CVE-2025-15330: Tanium Deploy · Missing Authorization
Affects Tanium DeploySource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 2.30.175 or 2.26.1279 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.30.175, 2.26.1279
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 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.
What to do
Upgrade Tanium Deploy to 2.30.175 or 2.26.1279.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TaniumDeploy | Affected
| Fixed in
|
| TaniumDeploy | Affected
| Fixed in
|
CPE configurations (2)
cpe:2.3:a:tanium:service_deploy:2.26.1278:*:*:*:*:*:*:*cpe:2.3:a:tanium:service_deploy:2.30.174:*:*:*:*:*:*:*
AI-suggested
European organizations should immediately verify their Tanium Deploy versions and upgrade to patched versions once available from the vendor. In the absence of patches, implement strict network segmentation to limit access to Tanium Deploy interfaces only to trusted administrators and systems. Enforce the principle of least privilege by reviewing and restricting user permissions within Tanium Deploy to minimize the number of accounts with low privileges that could be leveraged for exploitation. Enable detailed logging and monitoring of Tanium Deploy activities to detect anomalous behavior indicative of exploitation attempts. Employ multi-factor authentication (MFA) for all administrative access to reduce the risk of credential compromise. Conduct regular vulnerability assessments and penetration testing focused on Tanium Deploy components. Coordinate with Tanium support and subscribe to their security advisories to receive timely updates. Finally, prepare incident response plans that include scenarios involving Tanium Deploy compromise to ensure rapid containment and recovery.
Description
Tanium addressed an improper input validation vulnerability in Deploy.