Physical access to services via charging cable
Published Mar 10, 2026 · Updated Mar 10, 2026
Improper access control in Siemens Heliox EV chargers allows physically proximate attackers to reach unauthorized services via a charging cable. Siemens identifies the charging-cable communication path as the locus but has not disclosed which services are exposed or how endpoint access control fails. Physical access to a charging connector is required, and Siemens does not identify the information available through the exposed services.
Summary
What happened
Improper access control in Siemens Heliox EV chargers allows physically proximate attackers to reach unauthorized services via a charging cable. Siemens identifies the charging-cable communication path as the locus but has not disclosed which services are exposed or how endpoint access control fails. Physical access to a charging connector is required, and Siemens does not identify the information available through the exposed services.
The record
- CVE
- CVE-2025-27769
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Siemens
- Product
- Heliox Mobile DC 40 kW EV Charging Station
- Classifications
- CWE-923
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <L4.10.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo