# CVE-2026-102371: wsl-pro-service: Ubuntu Pro token exposed via process command-line arguments

> An unprivileged local user can read the Ubuntu Pro token from process arguments, allowing unauthorized access to Ubuntu Pro services.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-j32v-fr72-w8fv, UBUNTU-CVE-2026-102371, USN-8892-1

## What is CVE-2026-102371?

CVE-2026-102371 is a medium-severity vulnerability in Canonical Ubuntu Pro for WSL, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In wsl-pro-service before 0.1.19ubuntu3, the service component which runs as root inside each WSL instance attaches the instance to Ubuntu Pro by executing the pro client with the Ubuntu Pro token passed as a command-line argument (pro attach <token>). On systems where /proc is mounted without process-hiding mitigations (such as hidepid), which is the default in WSL, an unprivileged local user or process in the same WSL instance can read the token from /proc/<pid>/cmdline while the attach process is running. The leaked token could then be used to attach other machines to the victim's Ubuntu Pro subscription and gain unauthorized access to Ubuntu Pro services.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-102371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102371 is a medium-severity vulnerability in Canonical Ubuntu Pro for WSL, published on 29 Sep 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-102371 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Pro for WSL. 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-102371/ (Markdown: https://insights.sbomify.com/CVE-2026-102371/index.md)
```

## Sources

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

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