# CVE-2025-15326: Tanium addressed an improper access controls vulnerability in Patch.

> Attackers can bypass access controls in Tanium Patch to perform unauthorized actions, requiring immediate patching by administrators.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-vpmf-qv5h-69q8

## What is CVE-2025-15326?

CVE-2025-15326 is a medium-severity missing authorization vulnerability in Tanium Patch, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tanium addressed an improper access controls vulnerability in Patch.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Tanium Patch.

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

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

## Is CVE-2025-15326 being exploited?

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

## Other vulnerabilities in Tanium Patch

- [CVE-2025-15337](https://insights.sbomify.com/CVE-2025-15337/): Tanium addressed an incorrect default permissions vulnerability in Patch. (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15326 is a medium-severity missing authorization vulnerability in Tanium Patch, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15326 in the wild and no public exploit code.

Affected product: Tanium Patch. 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-15326/ (Markdown: https://insights.sbomify.com/CVE-2025-15326/index.md)
```

## Sources

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

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