CVE-2026-101054

Thinkware U3000 TCP Service wpa_supplicant.conf get_file access control

  • Medium 6.9
  • A public exploit reference is listed

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.

Key facts

Published
28 Sep 2026
Last changed
1 Oct 2026
Assigned by
VulDB
EPSS
0.286% likely to be exploited in the next 30 days, higher than 21.406% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.9CVSS 4.0, Mediumfrom the CNA (VulDB)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
  • 5.3CVSS 3.1, Mediumfrom the CNA (VulDB)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
  • 5.3CVSS 3.0, Mediumfrom the CNA (VulDB)CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
  • 5.0CVSS 2.0, Mediumfrom the CNA (VulDB)AV:N/AC:L/Au:N/C:P/I:N/A:N/E:POC/RL:ND/RC:UR

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
ThinkwareU3000
  • 1.02.04 (affected)

Timeline

  1. 27 Sep 2026 Advisory disclosed
  2. 27 Sep 2026 VulDB entry created
  3. 27 Sep 2026 VulDB entry last update
  4. 28 Sep 2026 Published

Weakness

References