Skip to content
IoT

CVE-2026-62928

9.3
Critical
EPSS 1%Sep 4, 2026

Unauthenticated OS command injection in XING CPTrans-ME-X device

common questions

Is CVE-2026-62928 being exploited?

Not confirmed. CVE-2026-62928 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 1.2% probability of exploitation in the next 30 days.

How severe is CVE-2026-62928?

CVE-2026-62928 is rated Critical with a CVSS score of 9.3. 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-62928?

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

CVE-2026-62928 affects XING CPTrans-ME-X, Embedded web/management interface, Rack accessory firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62928?

Isolate devices, block remote access, monitor, 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
XING CPTrans-ME-XEmbedded web/management interfaceRack accessory firmware
impact

Unauthenticated remote OS command execution allowing full device compromise, arbitrary commands, and lateral pivoting into networks.

action required

Immediate action required

affected versions
Xing Inc. XING CPTrans-ME-X
  • affected< 1.8.1.17

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