{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9038 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9038 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-9038 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-9038 in the wild and no public exploit code.\n\nAffected product: XCharge C6. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-9038/ (Markdown: https://insights.sbomify.com/CVE-2026-9038/index.md)","id":"CVE-2026-9038","markdown":"https://insights.sbomify.com/CVE-2026-9038/index.md","name":"CVE-2026-9038","record":{"aliases":["GHSA-88gx-5947-cmjp"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging controller","requires_auth":"none","summary":"An attacker with physical access can trigger a stack-based buffer overflow in the XCharge C6 controller to execute unauthorized code with elevated privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"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","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Stack-based buffer overflow in XCharge C6","id":"CVE-2026-9038","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Initialization of a resource with an insecure default in XCharge C6","id":"CVE-2026-9039"},"packages":[],"prev":{"headline":"Download of code without integrity check in XCharge C6","id":"CVE-2026-9037"},"products":["C6"],"published":"2026-05-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["XCharge"]},"summary":"An attacker with physical access can trigger a stack-based buffer overflow in the XCharge C6 controller to execute unauthorized code with elevated privileges.","url":"https://insights.sbomify.com/CVE-2026-9038/"}