Is CVE-2026-44104 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44104 being exploited in the wild.

How severe is CVE-2026-44104?

Critical severity, with a CVSS score of 9.8, published 30 July 2026.

Which products and versions are affected?

Phoenix Contact CHARX SEC-3000 < 1.9.1; Phoenix Contact CHARX SEC-3050 < 1.9.1; Phoenix Contact CHARX SEC-3100 < 1.9.1; Phoenix Contact CHARX SEC-3150 < 1.9.1.

Is there a fix for CVE-2026-44104?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-44104 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44104?

Check whether you run Phoenix Contact CHARX SEC-3000, Phoenix Contact CHARX SEC-3050, Phoenix Contact CHARX SEC-3100 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44104: Phoenix Contact CHARX SEC firmware update signature bypass

Q: Is there a fix for CVE-2026-44104?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-44104 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-44104?

Check whether you run Phoenix Contact CHARX SEC-3000, Phoenix Contact CHARX SEC-3050, Phoenix Contact CHARX SEC-3100 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44104 · Severity: critical · CVSS 9.8 · Published 2026-07-30

Phoenix Contact CHARX charging controllers, used to manage electric vehicle charging stations, contain a flaw in how they handle software updates. The system only checks for basic data errors rather than verifying that the update is authentic and comes from the manufacturer. This allows a remote attacker to install malicious software on the controller, potentially taking full control of the charging station and disrupting operations.

Technologies: Phoenix Contact CHARX SEC-3000, Phoenix Contact CHARX SEC-3050, Phoenix Contact CHARX SEC-3100, Phoenix Contact CHARX SEC-3150. Vendors: Phoenix Contact.

Quick answers

Is CVE-2026-44104 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44104 being exploited in the wild.
How severe is CVE-2026-44104?: Critical severity, with a CVSS score of 9.8, published 30 July 2026.
Which products and versions are affected?: Phoenix Contact CHARX SEC-3000 < 1.9.1; Phoenix Contact CHARX SEC-3050 < 1.9.1; Phoenix Contact CHARX SEC-3100 < 1.9.1; Phoenix Contact CHARX SEC-3150 < 1.9.1.
Is there a fix for CVE-2026-44104?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-44104 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44104?: Check whether you run Phoenix Contact CHARX SEC-3000, Phoenix Contact CHARX SEC-3050, Phoenix Contact CHARX SEC-3100 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The firmware update process for the basemodule of CHARX SEC-3xxx charging controllers (models 3000, 3050, 3100, and 3150) only validates the CRC32 checksum of update packages. It lacks cryptographic signature verification (CWE-347), which is necessary to ensure the authenticity and integrity of the firmware. An unauthenticated remote attacker can exploit this by delivering a modified or malicious firmware image to the device. Successful exploitation results in full system compromise, including loss of confidentiality, integrity, and availability. The vulnerability is addressed in firmware version 1.9.1.

Affected products

Phoenix Contact CHARX SEC-3000 < 1.9.1
Phoenix Contact CHARX SEC-3050 < 1.9.1
Phoenix Contact CHARX SEC-3100 < 1.9.1
Phoenix Contact CHARX SEC-3150 < 1.9.1

Timeline

2026-07-30: advisory: VDE-2026-008 published by CERT VDE
2026-07-30: disclosed: CVE-2026-44104 published to NVD

References

https://www.certvde.com/en/advisories/VDE-2026-008/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.