Skip to main content

Phoenix Contact CHARX SEC CVE-2026-44096

| EUVDEUVD-2026-51031 HIGH
OS Command Injection (CWE-78)
2026-07-30 info@cert.vde.com GHSA-rrvj-gc4g-ccjf
8.5
CVSS 4.0 · Vendor: cert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain charx-web local account
  2. Delivery
    Reach udhcpc command path
  3. Exploit
    Inject shell metacharacters into DHCP option
  4. Execution
    Command executed by root script
  5. Impact
    Full root compromise of controller

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to already hold the local, low-privileged 'charx-web' account on the CHARX SEC device and to reach the udhcpc-driven command path that runs as root; per the CVSS vector (AV:L/PR:L/UI:N) this is local and authenticated with no user interaction. The limiting factors are the need for that pre-existing 'charx-web' foothold and local access to the device - it is not remotely exploitable by an unauthenticated network attacker against a default configuration - while the absence of any UI or high-privilege requirement means that once the foothold is held, escalation to root is low-complexity and reliable.

Impact

The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H, base 8.5) describes a locally-exploitable but reliable path: no user interaction, low attack complexity, and only low existing privileges (the 'charx-web' account) needed to gain full confidentiality, integrity and availability impact as root. Because the attack vector is Local rather than Network, remote mass exploitation is not the concern; the realistic threat is any actor or chained web-facing flaw that first obtains the 'charx-web' foothold and then escalates to root. No EPSS score, KEV listing, or public POC was provided, so there is no evidence of active or widespread exploitation - this is a high-severity, high-impact issue whose priority is driven by the criticality of the OT/EV-charging deployment rather than by observed exploitation. SSVC-style reading: exploitation is not currently observed, technical impact is total, but automatability is limited by the local-access precondition.

Exploit ScenarioDerived

An attacker who has obtained the low-privileged 'charx-web' account - for example via a phished credential or a chained web-interface weakness - invokes the vulnerable udhcpc command path and injects shell metacharacters that are executed by the root-context DHCP script. The result is arbitrary command execution as root and full compromise of the charging controller. No public exploit code was identified, and the local, low-complexity vector makes reliable exploitation straightforward once the foothold exists.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 30, 2026

Local privilege escalation in the Phoenix Contact CHARX SEC EV charging controllers (SEC-3000/3050/3100/3150, firmware 1.0.0 through 1.9.0) lets the low-privileged local account 'charx-web' inject and run arbitrary OS commands as root via the udhcpc DHCP client, yielding full device takeover. The flaw is a CWE-78 OS command injection reported by CERT@VDE, and a vendor patch (1.9.1) is available. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

RemediationAI

Upgrade the affected CHARX SEC controllers to firmware version 1.9.1 or later, which is the vendor-released patch; consult the CERT@VDE advisory VDE-2026-008 (https://www.certvde.com/en/advisories/VDE-2026-008/) for exact update packages and instructions per hardware model. Until the update can be applied, reduce exposure of the prerequisite 'charx-web' account by restricting and monitoring access to the device's web/management interface, placing the charging controllers on an isolated management VLAN, and limiting who can authenticate to that service - with the trade-off that these controls do not remove the underlying command-injection path and only shrink the population of actors who can reach it. Avoid exposing the management interface to untrusted networks, since a compromise of 'charx-web' is the pivot to root.

Affected VersionsENISA

CHARX SEC-3150 1.0.0 <1.9.1
CHARX SEC-3050 1.0.0 <1.9.1
CHARX SEC-3000 1.0.0 <1.9.1
CHARX SEC-3100 1.0.0 <1.9.1

Affected Packages

euvd charx_sec_3000 fix: 1.9.1
euvd charx_sec_3050 fix: 1.9.1
euvd charx_sec_3100 fix: 1.9.1
euvd charx_sec_3150 fix: 1.9.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

udhcpc is BusyBox's lightweight DHCP client, commonly embedded in Linux-based appliances such as these charging controllers. It invokes a configuration script (typically /usr/share/udhcpc/default.script) on lease events and exports DHCP-supplied option values into the script's environment. When those values, or a wrapping helper, are passed unsanitized into a shell context, an actor able to influence them achieves OS command injection - the CWE-78 root cause class cited here. In this case the exposed 'charx-web' web/service account can reach that command-execution path and have commands run under root, the context udhcpc's scripts execute in. The affected CPE set covers the CHARX SEC-3000, SEC-3050, SEC-3100 and SEC-3150 hardware variants.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cert) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.8 HIGH

Requires the local low-privileged charx-web account (AV:L, PR:L) with no user interaction and low complexity, yielding full root impact (C/I/A:H).

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cert).

CVSS VectorVendor: cert

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Jul 30, 2026 - 08:03 EUVD
CVE Published
Jul 30, 2026 - 07:16 cve.org
HIGH 8.5

DescriptionCVE.org

A privilege escalation vulnerability in udhcpc allows a local user "charx-web" to execute arbitrary commands as root, resulting in full system compromise.

Executive ViewAI

Why It Matters

Phoenix Contact CHARX SEC electric vehicle charging controllers running firmware 1.0.0 through 1.9.0 contain a local privilege escalation vulnerability enabling complete device takeover. Organizations deploying these controllers must immediately patch to firmware 1.9.1 to prevent facility disruption and maintain operational security.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Low
niche OT/EV charging controllers, industry-specific hardware footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy