CVE-2026-101053

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-28. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A vulnerability was determined in Thinkware U3000 up to 1.02.04. This impacts the function PUT_FILE of the file /tmp/wpa_supplicant.conf of the component TCP Service. Executing a manipulation of the argument path can lead to improper access controls. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
7.3
EG Score
7.3HIGHhigh confidence
EG Risk
48
EG Risk 48/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 28, 2026

Advisory Details (1)

Auto-updated Sep 28, 2026
No patch confirmed yet.
generic

disclosure-thinkware-u3000/findings/01-arbitrary-file-write.md at main · turretsec/disclosure-thinkware-u3000 · GitHub

https://github.com/turretsec/disclosure-thinkware-u3000/blob/main/findings/01-arbitrary-file-write.md

Vendor Advisories for CVE-2026-101053(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 02:21 UTCEG score recompute
  2. 2026-10-04 02:21 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 13:20 UTCGHSA enrichment
  5. 2026-10-03 00:18 UTCEG score recompute
  6. 2026-10-03 00:18 UTCGHSA enrichment
  7. 2026-10-02 11:16 UTCGHSA enrichment
  8. 2026-10-01 22:15 UTCEG score recompute
  9. 2026-10-01 22:15 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 09:12 UTCGHSA enrichment
  12. 2026-09-30 20:11 UTCEG score recompute
  13. 2026-09-30 20:11 UTCGHSA enrichment
  14. 2026-09-30 15:02 UTCEPSS rescore
  15. 2026-09-30 07:10 UTCGHSA enrichment
  16. 2026-09-29 18:08 UTCEG score recompute
  17. 2026-09-29 18:08 UTCGHSA enrichment
  18. 2026-09-29 15:20 UTCEPSS rescore
  19. 2026-09-29 04:30 UTCEG score recompute
  20. 2026-09-29 04:30 UTCGHSA enrichment
  21. 2026-09-28 15:28 UTCGHSA enrichment
  22. 2026-09-28 13:29 UTCEG score recompute
  23. 2026-09-28 13:29 UTCGHSA enrichment
  24. 2026-09-28 13:29 UTCNVD updateCVSS v4 → 5.5
  25. 2026-09-28 12:52 UTCEG score recompute
Show 7 more
  1. 2026-09-28 12:52 UTCGHSA enrichment
  2. 2026-09-28 12:52 UTCMITRE cvelistV5CVSS v4 → 6.9
  3. 2026-09-28 12:31 UTCEG score recompute
  4. 2026-09-28 12:31 UTCGHSA enrichment
  5. 2026-09-28 12:30 UTCNVD updateCVSS v4 → 5.5
  6. 2026-09-28 11:39 UTCEG score recompute
  7. 2026-09-28 11:36 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-101053?
CVE-2026-101053 is a high vulnerability published on September 28, 2026. A vulnerability was determined in Thinkware U3000 up to 1.02.04. This impacts the function PUTFILE of the file /tmp/wpasupplicant.conf of the component TCP Service. Executing a manipulation of the argument path can lead to improper access controls. The attack may be launched remotely. The exploit…
When was CVE-2026-101053 disclosed?
CVE-2026-101053 was first published on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101053 actively exploited?
CVE-2026-101053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101053?
CVE-2026-101053 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101053?
No fix for CVE-2026-101053 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-101053 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-101053

Explore →

Is Your Infrastructure Affected by CVE-2026-101053?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs