Threat Intelligence Database

CVE-2026-44107 is a high-severity vulnerability in the Phoenix Contact CHARX SEC-3150 charging controller. It allows an unauthenticated attacker to trigger a reboot of the device via Modbus TCP when the Modbus service is enabled and its listening port is open. This results in a denial-of-service condition. The vulnerability affects version 1.0.0 of the product. No official patch or remediation has been confirmed yet.

CVE-2026-44100 is a high-severity vulnerability in the Phoenix Contact CHARX SEC-3150 device, specifically in the CHARX JupiCore service. It allows unauthenticated remote attackers to reconfigure charging points, potentially leading to disclosure of charging point unique identifiers (UIDs), denial-of-service conditions, and file tampering. The vulnerability is due to missing authentication for critical functions (CWE-306). Only version 1.0.0 of the product is explicitly affected. No official patch or remediation guidance has been provided yet.

CVE-2026-44098 is an OS command injection vulnerability in Phoenix Contact CHARX SEC-3150 version 1.0.0. It allows an unauthenticated remote attacker who can bypass the firewall and control the OCPP backend to execute arbitrary OS commands as the limited user charx-oa. This could disrupt charging operations. The vulnerability has a high severity with a CVSS score of 8.8. No official patch or remediation guidance is currently available from the vendor.

CVE-2026-44097 is a vulnerability in Phoenix Contact CHARX SEC-3150 version 1.0.0 that allows a low-privileged remote attacker with operator access to upload arbitrary files via a REST endpoint intended for firmware updates. This can lead to persistent storage of attacker-controlled files and potentially exhaust system resources, causing a denial-of-service condition. The vulnerability has a medium severity rating with a CVSS score of 5.3. No official patch or remediation has been confirmed at this time.

CVE-2026-44091 is a high-severity vulnerability in Phoenix Contact CHARX SEC-3150 version 1.0.0. An unauthenticated remote attacker can post a malicious ID to the MQTT Broker, causing the system to create a new configuration entry. This behavior can lead to loss of system integrity and availability. No official patch or remediation guidance is currently available from the vendor.