# CVE-2026-9038: Stack-based buffer overflow in XCharge C6

> An attacker with physical access can trigger a stack-based buffer overflow in the XCharge C6 controller to execute unauthorized code with elevated privileges.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-88gx-5947-cmjp

## What is CVE-2026-9038?

CVE-2026-9038 is a high-severity memory corruption vulnerability in XCharge C6, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability in the charging controller’s signal-processing logic allows an attacker with physical access to the charging interface to supply message fields that exceed expected bounds. Because the input is not sufficiently validated, memory corruption may occur, which can lead to execution of unauthorized code with elevated privileges.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-9038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9038 is a high-severity memory corruption vulnerability in XCharge C6, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9038 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-9038/ (Markdown: https://insights.sbomify.com/CVE-2026-9038/index.md)
```

## Sources

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

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