# CVE-2026-9037: Download of code without integrity check in XCharge C6

> Attackers can install unauthorized firmware on XCharge C6 controllers due to missing signature validation, leading to high-privilege code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-6qw7-34qq-r69v

## What is CVE-2026-9037?

CVE-2026-9037 is a critical code injection vulnerability in XCharge C6, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A firmware update mechanism in the affected charging controller fails to validate the authenticity of firmware packages delivered through the device's management interface. Because cryptographic signatures are not verified, an attacker with the ability to interfere with or impersonate the management channel could cause the device to install an unauthorized firmware package. This condition could allow execution of unauthorized code with high privileges on the device.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-9037?


## How do I fix CVE-2026-9037?

No fix has been published for CVE-2026-9037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9037 being exploited?

There is no known exploitation of CVE-2026-9037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9037 and fix it if it is affected.

What it is: CVE-2026-9037 is a critical code injection vulnerability in XCharge C6, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9037 in the wild and no public exploit code.

Affected product: XCharge C6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9037/ (Markdown: https://insights.sbomify.com/CVE-2026-9037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9037
- OSV: https://osv.dev/vulnerability/CVE-2026-9037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9037/
Summaries are generated and may contain mistakes; the official description above is the record.