dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-9038

HIGH · 8.6 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stack-based buffer overflow vulnerability exists in the charging controller's signal-processing logic. An attacker with physical access can send message fields that exceed expected bounds, causing memory corruption on the stack and potentially enabling code execution with elevated privileges.

MitigationImplement strict input validation and bounds checking on all message fields in the signal-processing logic, and update firmware with secure coding practices to prevent buffer overflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify charging controller presence
    Inventory your system hardware and firmware components to determine if a charging controller with signal-processing logic is present. Look for firmware components labeled as charging controller, battery management, or power delivery controller.
    Affected if A charging controller with signal-processing capability is present in the environment
  2. Determine firmware version
    If a charging controller is identified, retrieve its firmware version through vendor-provided tools, debug interfaces, or system firmware inventories. Compare the installed version against any vendor-provided version ranges or release notes.
    Affected if The firmware version is unknown, unpatched, or falls within an affected version range that cannot be determined from available documentation
  3. Check signal-processing feature status
    Examine the charging controller configuration to determine if the signal-processing logic is enabled. Review firmware settings, debug configurations, or management interfaces that control message processing for the charging controller.
    Affected if Signal-processing logic is enabled and accessible on the charging controller
  4. Assess physical access exposure
    Evaluate whether the message interface on the charging controller is accessible to physical attackers. Check if debug ports, charging ports, or service interfaces are exposed and can be used to send custom message fields.
    Affected if Physical access to the charging controller message interface is possible and no additional authentication or restrictions are enforced on field sizes
  5. Verify message field validation
    Review any available firmware configuration, input validation settings, or security controls related to message field handling in the charging controller signal-processing code.
    Affected if Message field bounds checking or input validation is not visibly implemented or is disabled

If the environment contains a charging controller with signal-processing logic that is enabled and physically accessible, and the firmware version cannot be confirmed as patched or outside affected ranges, the environment may be affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and bounds checking on all message fields in the signal-processing logic, and update firmware with secure coding practices to prevent buffer overflows.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9038 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data