CVE-2026-44103: medium-severity vulnerability in Phoenix Contact CHARX SEC-3000
JupiCore does not perform validation of firmware
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.4%
An unauthenticated remote attacker can inject malicious firmware into the internal charging module because the JupiCore service transmits firmware updates without performing integrity or verification check. Successful exploitation may compromise the integrity of the affected device. This vulnerability could be used in chain with CVE-2026-44104.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
Phoenix Contact · CHARX SEC-3000Phoenix Contact · CHARX SEC-3050Phoenix Contact · CHARX SEC-3100Phoenix Contact · CHARX SEC-3150Related CVEs — Phoenix Contact CHARX SEC-3000
In the same product, most dangerous first.
CVE-2026-44098HIGHOS Command Injection in OCPP Agent via charge_box_idEPSS 1.7%CVE-2025-41699HIGHPhoenix Contact: Security Advisory for CHARX SEC-3xxx charging controllersEPSS 0.8%CVE-2026-44108CRITICALFirewall bypass during shutdownEPSS 0.8%CVE-2026-7849CRITICALCommand Injection in SCM (idledisconnect parameter)EPSS 0.8%CVE-2025-25270CRITICALRemote Code Execution via Unauthenticated Configuration ManipulationEPSS 0.8%CVE-2026-44101CRITICALOCPP reconfiguration vulnerabilityEPSS 0.7%