# CVE-2026-101054: Thinkware U3000 TCP Service wpa_supplicant.conf get_file access control

> Remote attackers can access the wpa_supplicant.conf file via the TCP service due to improper access controls, potentially exposing Wi-Fi credentials.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-mrrg-524v-2rf2

## What is CVE-2026-101054?

CVE-2026-101054 is a medium-severity missing authorization vulnerability in Thinkware U3000, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in Thinkware U3000 up to 1.02.04. Affected is the function get_file of the file /tmp/wpa_supplicant.conf of the component TCP Service. The manipulation leads to improper access controls. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-101054 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101054 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101054 is a medium-severity missing authorization vulnerability in Thinkware U3000, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101054 exists.

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

## Sources

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

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