Skip to content
IoT

CVE-2026-20744

CRITICAL
Critical
EPSS 0.76%Jul 11, 2026

Unauthenticated websocket allows privilege escalation on EV charging stations

common questions

Is CVE-2026-20744 being exploited?

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

How severe is CVE-2026-20744?

CVE-2026-20744 is rated Critical. 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-20744?

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

CVE-2026-20744 affects EV charging stations (websocket endpoint), Charge point controllers, Operator management systems. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-20744?

Isolate chargers, block websocket ports, apply network ACLs, monitor logs, deploy vendor patch when available

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

executive summary
technical analysis
affected
EV charging stations (websocket endpoint)Charge point controllersOperator management systems
impact

Remote attacker can connect to charger websocket without authentication to gain elevated control—modify sessions, firmware, billing, or device settings.

action required

Immediate action required

affected versions
Hydro-Québec Le Circuit Electrique charging station backend
  • affected< June_2026

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