Skip to content
IoT

CVE-2026-61892

8.7
High
EPSS 0.28%Jul 25, 2026

Local token modification allows privilege escalation on Weintek cMT3092X HMI

common questions

Is CVE-2026-61892 being exploited?

Not confirmed. CVE-2026-61892 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-61892?

CVE-2026-61892 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-61892?

Not known from our data. No patch reference has been recorded for CVE-2026-61892, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-61892 affect?

CVE-2026-61892 affects Weintek cMT3092X HMI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61892?

Restrict HMI network access, enforce strong auth, audit accounts, apply vendor patch when released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Weintek cMT3092X HMI
impact

Local non-privileged user can modify tokens to gain admin privileges, control HMI settings, disrupt ICS processes, or pivot on the network.

action required

Immediate action required

affected versions
Weintek cMT3092X firmware
  • affected< 20210218
Weintek EasyWeb
  • affected< v2.1.20
vendor says fixed in2.3.17-typeb

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free