Summary
Successful exploitation of these vulnerabilities could lead to privilege escalation, or result in a denial-of-service attack.
The following versions of Hydro-Québec Le Circuit Electrique charging station backend are affected:
- Le Circuit Electrique charging station backend
| CVSS | Vendor | Equipment | Vulnerabilities |
|---|---|---|---|
| v3 9.8 | Hydro-Québec | Hydro-Québec Le Circuit Electrique charging station backend | Improper Access Control, Improper Restriction of Excessive Authentication Attempts, Insufficient Session Expiration |
Background
- Critical Infrastructure Sectors: Transportation Systems
- Countries/Areas Deployed: Canada
- Company Headquarters Location: Canada
Vulnerabilities
CVE-2026-20744
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
Affected Products
Hydro-Québec Le Circuit Electrique charging station backend
Vendor:
Hydro-Québec
Product Version: Product Status:
Hydro-Québec Le Circuit Electrique charging station backend:
known_affected
Relevant CWE: CWE-284 Improper Access Control
Metrics
CVE-2026-42952
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a Denial-of-Service attack.
Affected Products
Hydro-Québec Le Circuit Electrique charging station backend
Vendor:
Hydro-Québec
Product Version: Product Status:
Hydro-Québec Le Circuit Electrique charging station backend:
known_affected
Relevant CWE: CWE-307 Improper Restriction of Excessive Authentication Attempts
Metrics
CVE-2026-44383
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Affected Products
Hydro-Québec Le Circuit Electrique charging station backend
Vendor:
Hydro-Québec
Product Version: Product Status:
Hydro-Québec Le Circuit Electrique charging station backend:
known_affected
Relevant CWE: CWE-613 Insufficient Session Expiration
Metrics
Acknowledgments
- An anonymous researcher reported these vulnerabilities to CISA
Legal Notice and Terms of Use
This product is provided subject to this Notification (https://www.cisa.gov/notification) and this Privacy & Use policy (https://www.cisa.gov/privacy-policy).
Recommended Practices
CISA recommends users take defensive measures to minimize the risk of exploitation of these vulnerabilities.
Minimize network exposure for all control system devices and/or systems, ensuring they are not accessible from the internet.
Locate control system networks and remote devices behind firewalls and isolating them from business networks.
When remote access is required, use more secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices.
CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.
CISA also provides a section for control systems security recommended practices on the ICS webpage on cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.
CISA encourages organizations to implement recommended cybersecurity strategies for proactive defense of ICS assets.
Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B–Targeted Cyber Intrusion Detection and Mitigation Strategies.
Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.
No known public exploitation specifically targeting these vulnerabilities has been reported to CISA at this time.
Revision History
- Initial Release Date: 2026-07-07
| Date | Revision | Summary |
|---|---|---|
| 2026-07-07 | 1 | Initial Publication |