Skip to content
IoT

CVE-2026-12562

8.7
High
EPSS 0.28%Jul 31, 2026

Unauthenticated debug service grants root access on RCU II+ and Multiload II+.

common questions

Is CVE-2026-12562 being exploited?

Not confirmed. CVE-2026-12562 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-12562?

CVE-2026-12562 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-12562?

Not known from our data. No patch reference has been recorded for CVE-2026-12562, 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-12562 affect?

CVE-2026-12562 affects RCU II+, Multiload II+, Devices running Target Communications Framework (TCF) debug service. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-12562?

Isolate devices, block TCF port, restrict network access, 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
RCU II+Multiload II+Devices running Target Communications Framework (TCF) debug service
impact

Unauthenticated remote root access via network TCF debug service; full filesystem, process, and network control.

action required

Immediate action required

affected versions
Toptech Systems Multiload II+
  • affected< 2025-11-24
Toptech Systems RCU II+
  • affected< 2025-11-24

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