dbcve.org
Home Flex Cph50 FirmwareOperating system · Chargepoint

CVE-2026-4156

HIGH · 7.5 CVSS v3.0 Published 2026-04-11
Fix available
A fix is available. Upgrade to 5.5.4.22 or later.
See remediation →
80/100
Remediation priority · High
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
ChargePoint Home Flex OCPP getpreq Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of ChargePoint Home Flex EV chargers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of OCPP messages. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-26339.

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

A stack-based buffer overflow vulnerability exists in the ChargePoint Home Flex EV charger's OCPP (Open Charge Point Protocol) message handling. The flaw results from insufficient length validation of user-supplied data before copying to a fixed-size stack buffer. This allows network-adjacent attackers to achieve remote code execution as root without authentication.

MitigationApply vendor firmware updates when available; until then, isolate EV chargers on a dedicated network segment with strict firewall rules limiting OCPP traffic to authorized management systems.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Home Flex Cph50 FirmwareOperating system
Affected:< 5.5.4.22

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the device model
    Locate the physical EV charger or check the device's web interface/mobile app to confirm it is a ChargePoint Home Flex Cph50 model
    Affected if The device is not a ChargePoint Home Flex Cph50, then this specific CVE does not apply
  2. Check the installed firmware version
    Access the ChargePoint app or web interface and navigate to Settings > About or Device Information to view the firmware version number
    Affected if The firmware version is lower than 5.5.4.22 (for example, 5.5.4.21 or earlier)
  3. Verify OCPP is enabled
    Check the device configuration settings for OCPP (Open Charge Point Protocol) connectivity. This is typically found in Network Settings, Connectivity options, or OCPP configuration menu in the charger's admin interface
    Affected if OCPP is actively configured and the charger is communicating with an OCPP central system or management platform
  4. Assess network exposure of OCPP service
    Review firewall rules and network segmentation to determine if the OCPP port (typically port 8080 or 8443 for OCPP) is accessible to untrusted network segments or the broader internet
    Affected if The OCPP interface is reachable from network segments outside the trusted management network, particularly from untrusted or guest networks

You are affected if you have a ChargePoint Home Flex Cph50 running firmware below 5.5.4.22 with OCPP enabled and exposed to untrusted network access.

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.

dbcve · scoped
Upgrade available Upgrade to 5.5.4.22 or later
Fixed in 5.5.4.22
Interim mitigation

Apply vendor firmware updates when available; until then, isolate EV chargers on a dedicated network segment with strict firewall rules limiting OCPP traffic to authorized management systems.

Recommended fix Moderate confidence

Home Flex Cph50 Firmware version 5.5.4.22 or later

  1. 1. Identify the current firmware version of the ChargePoint Home Flex Cph50 charger via the ChargePoint app or web interface
  2. 2. Navigate to the device settings or firmware management section
  3. 3. Check for and install any available firmware updates
  4. 4. Verify the firmware has been updated to version 5.5.4.22 or later
  5. 5. Confirm the update was successful and the device is functioning normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Home Flex Cph50 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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