Elevated code execution via oversized charging messages
Published May 28, 2026 · Updated May 28, 2026
Stack-based buffer overflow in XCharge C6 before May 22, 2026 allows physically proximate attackers to execute code with elevated privileges. The charging controller’s signal-processing logic fails to reject oversized message fields received through the charging interface, corrupting stack memory. Physical access to the charging connector is required, and successful exploitation runs unauthorized code with elevated privileges on the charger.
Summary
What happened
Stack-based buffer overflow in XCharge C6 before May 22, 2026 allows physically proximate attackers to execute code with elevated privileges. The charging controller’s signal-processing logic fails to reject oversized message fields received through the charging interface, corrupting stack memory. Physical access to the charging connector is required, and successful exploitation runs unauthorized code with elevated privileges on the charger.
The record
- CVE
- CVE-2026-9038
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- XCharge
- Product
- C6
- Classifications
- CWE-121
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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 <May_22_2026
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