# CVE-2025-15339: Tanium addressed an incorrect default permissions vulnerability in Discover.

> Attackers can exploit incorrect default permissions in Tanium Discover to bypass security controls.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-p973-6746-hp5x

## What is CVE-2025-15339?

CVE-2025-15339 is a medium-severity vulnerability in Tanium Discover, published on 5 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Tanium addressed an incorrect default permissions vulnerability in Discover.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2025-15339?

It affects 1 product.


Products: Tanium Discover.

## How do I fix CVE-2025-15339?

No fix has been published for CVE-2025-15339 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15339 being exploited?

There is no known exploitation of CVE-2025-15339 in the wild and no public exploit code.

## Other vulnerabilities in Tanium Discover

- [CVE-2025-15325](https://insights.sbomify.com/CVE-2025-15325/): Tanium addressed an improper input validation vulnerability in Discover. (medium 6.3)
- [CVE-2026-1224](https://insights.sbomify.com/CVE-2026-1224/): Tanium addressed an uncontrolled resource consumption vulnerability in Discover. (medium 4.9)
- [CVE-2026-0925](https://insights.sbomify.com/CVE-2026-0925/): Tanium addressed an improper input validation vulnerability in Discover. (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15339 and fix it if it is affected.

What it is: CVE-2025-15339 is a medium-severity vulnerability in Tanium Discover, published on 5 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15339 in the wild and no public exploit code.

Affected product: Tanium Discover. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15339/ (Markdown: https://insights.sbomify.com/CVE-2025-15339/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15339
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15339
- OSV: https://osv.dev/vulnerability/CVE-2025-15339

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15339/
Summaries are generated and may contain mistakes; the official description above is the record.