dbcve.org
End User CxApplication · Tanium

CVE-2025-15314

HIGH · 8.1 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 1.4.1175 / 1.6.926 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Tanium addressed an arbitrary file deletion vulnerability in end-user-cx.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Tanium end-user-cx component contains an arbitrary file deletion vulnerability that could allow an attacker to delete files on the system. The high CVSS score (8.1) indicates significant potential impact, likely requiring authenticated access to exploit.

MitigationApply the vendor patch or update to the Tanium end-user-cx component as provided by Tanium to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
End User CxApplication
Affected:>= 1.4, < 1.4.1175>= 1.6, < 1.6.926>= 1.8, < 1.8.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Tanium end-user-cx component is present
    Check for the presence of the Tanium end-user-cx module or service in your Tanium deployment. This is typically managed through the Tanium console or by querying the Tanium server for installed modules.
    Affected if The component is not found or not installed, then this CVE does not apply to your environment.
  2. Determine the installed version of end-user-cx
    Use the Tanium console or command-line interface to query the version of the end-user-cx component. Look for a version number in the format such as 1.4.x, 1.6.x, or 1.8.x.
    Affected if You cannot determine the version - further investigation may be required to confirm your exposure.
  3. Compare version 1.4.x against affected range
    If the installed version starts with 1.4, verify whether it is lower than 1.4.1175. Versions 1.4.1175 and above are not affected.
    Affected if The installed 1.4.x version is below 1.4.1175 - your environment is affected by this vulnerability.
  4. Compare version 1.6.x against affected range
    If the installed version starts with 1.6, verify whether it is lower than 1.6.926. Versions 1.6.926 and above are not affected.
    Affected if The installed 1.6.x version is below 1.6.926 - your environment is affected by this vulnerability.
  5. Compare version 1.8.x against affected range
    If the installed version starts with 1.8, verify whether it is lower than 1.8.21. Versions 1.8.21 and above are not affected.
    Affected if The installed 1.8.x version is below 1.8.21 - your environment is affected by this vulnerability.

Your environment is affected if the Tanium end-user-cx component is installed and its version falls within any of these ranges: 1.4.x below 1.4.1175, 1.6.x below 1.6.926, or 1.8.x below 1.8.21.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.1175 / 1.6.926 / 1.8.21 or later
Fixed in 1.4.11751.6.9261.8.21
Interim mitigation

Apply the vendor patch or update to the Tanium end-user-cx component as provided by Tanium to remediate this vulnerability.

Recommended fix High confidence

End User Cx 1.4.1175 (for 1.4.x branch), 1.6.926 (for 1.6.x branch), or 1.8.21 (for 1.8.x branch)

  1. Identify the currently installed End User Cx version using the Tanium console or command-line tools
  2. Determine which version branch (1.4.x, 1.6.x, or 1.8.x) is currently in use
  3. For systems running >= 1.4.x and < 1.4.1175: Upgrade to version 1.4.1175 or later
  4. For systems running >= 1.6.x and < 1.6.926: Upgrade to version 1.6.926 or later
  5. For systems running >= 1.8.x and < 1.8.21: Upgrade to version 1.8.21 or later
  6. After upgrade, verify the new version is running and confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in End User Cx Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15314 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data