CVE-2026-44102: Phoenix Contact CHARX SEC race condition in firmware update cleanup

CVE-2026-44102 · Severity: medium · CVSS 5.3 · Published 2026-07-30

Phoenix Contact CHARX SEC charging controllers, which manage electric vehicle charging stations, are affected by a race condition during firmware updates. An unauthenticated attacker can trigger a download of an invalid firmware file, which remains accessible on the device for a short period due to improper cleanup. This could allow an attacker to interfere with the device's file system or integrity during the update process.

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-44102 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44102 being exploited in the wild.
How severe is CVE-2026-44102?
Medium severity, with a CVSS score of 5.3, 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-44102?
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-44102 attacked?
It is attacked over the network, in device firmware.
Am I affected by CVE-2026-44102?
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

A race condition (CWE-362) exists in the firmware update cleanup process of Phoenix Contact CHARX SEC-3xxx devices. An unauthenticated remote attacker can initiate a firmware download via the Open Charge Point Protocol (OCPP) backend by providing an invalid firmware file. Due to improper locking during the cleanup phase, the invalid file is not immediately deleted, leaving a window of time where the file remains accessible on the system. This vulnerability affects firmware versions prior to 1.9.1. An attacker can exploit this to impact the integrity of the device's storage or potentially facilitate further attacks during the update window.

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-44102 published

References

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