dbcve.org
Module ServerPlugin / extension · Tanium

CVE-2025-15315

HIGH · 7.8 CVSS v3.1 Published 2026-02-09
Fix available
A fix is available. Upgrade to 7.4.6.1151 / 7.5.6.1161 or later.
See remediation →
80/100
Remediation priority · High
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 a local privilege escalation vulnerability in Tanium Module Server.

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 Module Server contained a local privilege escalation vulnerability that allowed an authenticated local attacker to elevate privileges. This was addressed by Tanium through a vendor patch.

MitigationApply the Tanium security update/patch for Module Server as provided by Tanium. Verify the patch version matches the vendor's corrected release.

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
Module ServerPlugin / extension
Affected:>= 7.4.6, < 7.4.6.1151>= 7.5.6, < 7.5.6.1161>= 7.6.2, < 7.6.2.1293>= 7.6.4, < 7.6.4.2114
ServerApplication
Affected:>= 7.4.6, < 7.4.6.1151>= 7.5.6, < 7.5.6.1161>= 7.6.2, < 7.6.2.1293>= 7.6.4, < 7.6.4.2114

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 installation and version
    Locate Tanium installation directories and identify the installed version of Tanium Server or Module Server component
    Affected if Tanium is installed and the version falls within the affected ranges (7.4.6 to 7.4.6.1151, 7.5.6 to 7.5.6.1161, 7.6.2 to 7.6.2.1293, or 7.6.4 to 7.6.4.2114)
  2. Confirm Module Server component is present
    Verify that the Tanium Module Server component is installed on the system
    Affected if Module Server component is present and the version is within the affected ranges listed above
  3. Compare installed version against affected ranges
    Document the exact version number of the installed Tanium Server or Module Server and compare it against the vulnerable version ranges
    Affected if The installed version is greater than or equal to 7.4.6 but less than 7.4.6.1151; OR greater than or equal to 7.5.6 but less than 7.5.6.1161; OR greater than or equal to 7.6.2 but less than 7.6.2.1293; OR greater than or equal to 7.6.4 but less than 7.6.4.2114
  4. Verify local user access exists
    Assess whether local authenticated users exist on the system who could potentially exploit this privilege escalation vulnerability
    Affected if Local authenticated users are present on the system running the affected Tanium version

A system is affected if it is running Tanium Server or Tanium Module Server with a version that falls within any of the four vulnerable ranges and local authenticated user access is possible.

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 7.4.6.1151 / 7.5.6.1161 / 7.6.2.1293 or later
Fixed in 7.4.6.11517.5.6.11617.6.2.1293
Interim mitigation

Apply the Tanium security update/patch for Module Server as provided by Tanium. Verify the patch version matches the vendor's corrected release.

Recommended fix High confidence

Upgrade to 7.4.6.1151 (or latest 7.4.x), 7.5.6.1161 (or latest 7.5.x), 7.6.2.1293 (or latest 7.6.2.x), or 7.6.4.2114 (or latest 7.6.4.x) depending on your current branch

  1. Identify the currently installed Tanium Server and Module Server version using the Tanium console or command line
  2. Determine which version branch (7.4.x, 7.5.x, 7.6.2.x, or 7.6.4.x) is currently in use
  3. Download the appropriate fixed version from the Tanium customer portal or official distribution channels
  4. Review Tanium upgrade documentation and ensure backup procedures are in place
  5. Schedule a maintenance window to minimize production impact
  6. Upgrade the Module Server component to the fixed version (7.4.6.1151+, 7.5.6.1161+, 7.6.2.1293+, or 7.6.4.2114+)
  7. Verify the upgrade was successful by checking the version in the Tanium console
  8. Confirm the vulnerability is remediated by reviewing the security release notes
Caveat Review Tanium release notes for any breaking changes between your current version and the target fixed version before upgrading

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

Fix this in Module Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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