dbcve.org
Home Flex Cph50 FirmwareOperating system · Chargepoint

CVE-2026-4157

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 revssh Service Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of ChargePoint Home Flex devices. 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 a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-26338.

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

The ChargePoint Home Flex revssh service contains a command injection vulnerability in its OCPP message handling. The flaw stems from insufficient validation of user-supplied strings before they are passed to system calls, allowing unauthenticated attackers to execute arbitrary code with root privileges.

MitigationApply vendor-supplied firmware updates when available. As an interim measure, restrict network access to the device's management interface and segment it from untrusted networks.

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
    Access the device management interface or check the device label to confirm it is a ChargePoint Home Flex Cph50 model
    Affected if The device is not a ChargePoint Home Flex Cph50 model - different models are not affected by this specific vulnerability
  2. Check the installed firmware version
    Log into the ChargePoint device management interface and navigate to Settings > About or use the ChargePoint app to view the firmware version information
    Affected if The firmware version is lower than 5.5.4.22 (for example, 5.5.4.20 or earlier)
  3. Verify if the revssh service is accessible
    Check network configuration or use a port scanner targeting port 22 (or the configured SSH port) on the device IP address to determine if the revssh service is exposed
    Affected if The revssh service is accessible from an untrusted network - the vulnerability can only be exploited if the service accepts connections
  4. Confirm OCPP message handling is enabled
    Check the device configuration for OCPP (Open Charge Point Protocol) settings - this is typically configured if the charger is connected to a charge point management system or network operator
    Affected if OCPP message handling is enabled and the device communicates with external OCPP servers - the command injection occurs in OCPP message processing

The environment is affected if it is a ChargePoint Home Flex Cph50 device running firmware version 5.5.4.22 or lower, with the revssh service network-accessible and OCPP messaging enabled.

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-supplied firmware updates when available. As an interim measure, restrict network access to the device's management interface and segment it from untrusted networks.

Recommended fix High confidence

Firmware 5.5.4.22 or later

  1. Identify the current firmware version of the ChargePoint Home Flex Cph50 device
  2. Download the latest firmware version 5.5.4.22 or later from the official ChargePoint support website
  3. Follow ChargePoint's official firmware update instructions to apply the update
  4. Verify the firmware has been successfully updated to version 5.5.4.22 or later
  5. Confirm the revssh service is running the updated version
Caveat Review ChargePoint release notes for any changes to device functionality or configuration requirements before upgrading

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

Fix this in Home Flex Cph50 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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