# CVE-2026-12139: Tanium addressed an information disclosure vulnerability in Connect.

> An attacker can access sensitive information from Tanium Connect, requiring a patch to mitigate the risk.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-w2w5-6rpf-f2w8

## What is CVE-2026-12139?

CVE-2026-12139 is a medium-severity vulnerability in Tanium Connect, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tanium addressed an information disclosure vulnerability in Connect.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information)

## Which versions are affected by CVE-2026-12139?

It affects 1 product.


Products: Tanium Connect.

## How do I fix CVE-2026-12139?

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

## Is CVE-2026-12139 being exploited?

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

## Other vulnerabilities in Tanium Connect

- [CVE-2026-9207](https://insights.sbomify.com/CVE-2026-9207/): Tanium addressed an unauthorized code execution vulnerability in Connect. (high 8.8)
- [CVE-2026-9208](https://insights.sbomify.com/CVE-2026-9208/): Tanium addressed an unauthorized code execution vulnerability in Connect. (high 8.8)
- [CVE-2025-15331](https://insights.sbomify.com/CVE-2025-15331/): Tanium addressed an uncontrolled resource consumption vulnerability in Connect. (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12139 and fix it if it is affected.

What it is: CVE-2026-12139 is a medium-severity vulnerability in Tanium Connect, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12139 in the wild and no public exploit code.

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

## Sources

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

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