dbcve.org
End User NotificationsApplication · Tanium

CVE-2025-15318

MEDIUM · 6.0 CVSS v3.1 Published 2026-02-09
Fix available
A fix is available. Upgrade to 1.18.10079 / 10.0.14 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Notifications Endpoint Tools.

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 Notifications Endpoint Tools contained an arbitrary file deletion vulnerability allowing unauthorized deletion of files on affected systems. This was addressed by Tanium through a vendor patch.

MitigationApply the Tanium vendor patch for CVE-2025-15318 to all affected End-User Notifications Endpoint Tools installations.

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 NotificationsApplication
Affected:>= 1.18, < 1.18.10079>= 10.0, < 10.0.14>= 10.1, < 10.1.20

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 Tanium End-User Notifications installation
    Check for Tanium End-User Notifications Endpoint Tools installation using system inventory tools, registry keys, or installed programs list. Look for entries named 'Tanium End User Notifications' or similar Tanium components.
    Affected if The software is installed on the system
  2. Determine installed version
    Query the installed version of Tanium End-User Notifications. This may be available via Tanium console, in installed program details, or via Tanium client commands such as 'taniumctl version' or similar endpoint tool queries.
    Affected if The installed version falls within the affected ranges: 1.18.x before 1.18.10079, 10.0.x before 10.0.14, or 10.1.x before 10.1.20
  3. Verify End-User Notifications service status
    Check if the End-User Notifications endpoint tool service or module is actively running or enabled on the endpoint. This can be done via Tanium console endpoint details or system service queries.
    Affected if The End-User Notifications service is installed and running

The system is affected if Tanium End-User Notifications Endpoint Tools is installed with a version matching the affected ranges (1.18.x before 1.18.10079, 10.0.x before 10.0.14, or 10.1.x before 10.1.20) and the notification service is active.

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.18.10079 / 10.0.14 / 10.1.20 or later
Fixed in 1.18.1007910.0.1410.1.20
Interim mitigation

Apply the Tanium vendor patch for CVE-2025-15318 to all affected End-User Notifications Endpoint Tools installations.

Recommended fix Moderate confidence

Upgrade to 1.18.10079 (for 1.18 branch), 10.0.14 (for 10.0 branch), or 10.1.20 (for 10.1 branch) - choose the appropriate version based on your current branch

  1. 1. Identify the current version of Tanium End-User Notifications deployed in your environment
  2. 2. Determine which version branch your installation belongs to (1.18.x, 10.0.x, or 10.1.x)
  3. 3. For version 1.18.x: upgrade End User Notifications to version 1.18.10079 or later
  4. 4. For version 10.0.x: upgrade End User Notifications to version 10.0.14 or later
  5. 5. For version 10.1.x: upgrade End User Notifications to version 10.1.20 or later
  6. 6. After upgrade, verify the new version is running and the vulnerability is resolved

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

Fix this in End User Notifications Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15318 — 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-15318 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