dbcve.org
CWE-494Weakness · CWE-494

CVE-2026-9037

CRITICAL · 9.3 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 →
100/100
Remediation priority · Urgent
Remotely reachable 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 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.

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 · high confidence

The charging controller's firmware update mechanism lacks cryptographic signature verification, allowing attackers to deliver malicious firmware through the management interface. Since the authenticity of firmware packages is not validated before installation, an attacker who can intercept or impersonate the management channel can cause the device to install compromised firmware and execute code with high privileges.

MitigationImplement cryptographic signature verification for all firmware updates, ensuring each package is signed by a trusted key and validated before execution. Additionally, secure the management channel using TLS or equivalent encryption to prevent interception and impersonation attacks.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/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 device type
    Check if the device is a charging controller or manages charging infrastructure by reviewing device inventory, management console, or system documentation
    Affected if Device is a charging controller or related firmware update system
  2. Locate firmware update interface
    Access the device management console or CLI and navigate to firmware update, upgrade, or software management sections to confirm the update mechanism exists
    Affected if Firmware update capability is present and accessible via management interface
  3. Verify signature verification configuration
    Check firmware update settings for cryptographic signature verification, secure boot, or integrity check options - look for settings named 'signature verification', 'secure boot', 'verify firmware', 'checksum validation', or similar
    Affected if Signature verification is disabled, not configured, or option is absent from firmware update settings
  4. Inspect management channel security
    Review management interface configuration for TLS/SSL enforcement, authentication requirements, and access controls - check if management channel is protected against interception
    Affected if Management interface lacks encryption, uses weak authentication, or allows unauthenticated access to firmware update functionality
  5. Check firmware metadata for signatures
    If firmware files are accessible, inspect them for digital signatures, certificates, or integrity metadata using file analysis tools or vendor documentation
    Affected if Firmware files contain no cryptographic signatures or integrity verification data

The environment is affected if the charging controller has a firmware update mechanism that does not enforce cryptographic signature verification before accepting and installing firmware updates.

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 cryptographic signature verification for all firmware updates, ensuring each package is signed by a trusted key and validated before execution. Additionally, secure the management channel using TLS or equivalent encryption to prevent interception and impersonation attacks.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
88.0 hours of engineering $15,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9037 — 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-9037 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