CVE-2025-15310
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 · uneditedTanium addressed a local privilege escalation vulnerability in Patch 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 · low confidenceLocal privilege escalation vulnerability in Tanium Patch Endpoint Tools that allows an authenticated local attacker to gain elevated privileges on the affected system.
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< 1.40.37>= 3.17, < 3.17.10195>= 10.1, < 10.1.33>= 10.2, < 10.2.22CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Tanium Patch Endpoint Tools is installedCheck for TaniumPatch or related Tanium service processes running on the system, or look for Tanium installation directories (typically under C:\Program Files\Tanium\Tanium Patch or similar paths on Windows, or /opt/Tanium/ on Linux)Affected if Tanium Patch Endpoint Tools software is present on the system
-
Determine the installed version of Tanium Patch Endpoint ToolsCheck the product version information - this is typically available in the Windows Add/Remove Programs list, the Tanium client interface, or version files within the Tanium installation directoryAffected if The installed version falls within any of these ranges: >= 3.17 and < 3.17.10195; >= 10.1 and < 10.1.33; >= 10.2 and < 10.2.22
-
Identify if Tanium Endpoint Configuration Toolset Solution is installedCheck for Tanium Endpoint Configuration Toolset components or related services, or look for this toolset in the Tanium module list if accessibleAffected if Tanium Endpoint Configuration Toolset Solution is present on the system
-
Determine the installed version of Tanium Endpoint Configuration ToolsetCheck the product version for the Endpoint Configuration Toolset Solution - typically available through Tanium console, installed module list, or version metadata in the Tanium directoryAffected if The installed version is less than 1.40.37
-
Verify local authenticated access existsThis vulnerability requires an authenticated local attacker. Confirm whether untrusted local user accounts exist on the system with access to the Tanium environmentAffected if Untrusted or low-privilege local user accounts have access to the system where Tanium software is running
A system is affected if Tanium Patch Endpoint Tools version is 3.17.x up to 3.17.10194, 10.1.x up to 10.1.32, or 10.2.x up to 10.2.21; OR Tanium Endpoint Configuration Toolset Solution is version 1.40.36 or lower, and the system has local user accounts that could exploit the privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.40.373.17.1019510.1.33
Apply the vendor patch or update to Tanium Patch Endpoint Tools as released by Tanium.
Endpoint Configuration Toolset Solution >= 1.40.37; Patch Endpoint Tools >= 3.17.10195 (3.x branch), >= 10.1.33 (10.1.x branch), or >= 10.2.22 (10.2.x branch)
- 1. Identify the currently installed version of Tanium Patch Endpoint Tools or Endpoint Configuration Toolset Solution on the affected system
- 2. Determine which product and version branch is in use (Endpoint Configuration Toolset Solution, or Patch Endpoint Tools version 3.x, 10.1.x, or 10.2.x)
- 3. For Endpoint Configuration Toolset Solution: upgrade to version 1.40.37 or later
- 4. For Patch Endpoint Tools version 3.x: upgrade to version 3.17.10195 or later
- 5. For Patch Endpoint Tools version 10.1.x: upgrade to version 10.1.33 or later
- 6. For Patch Endpoint Tools version 10.2.x: upgrade to version 10.2.22 or later
- 7. Verify the upgrade was successful by confirming the installed version matches or exceeds the minimum fixed version
- 8. Test that Patch Endpoint Tools functionality operates normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15310 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15310 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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