Quick answers
- Is CVE-2026-44103 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44103 being exploited in the wild.
- How severe is CVE-2026-44103?
- Medium severity, with a CVSS score of 5.3, published 30 July 2026.
- Which products and versions are affected?
- Phoenix Contact CHARX SEC-3000 Firmware < 1.9.1; Phoenix Contact CHARX SEC-3050 Firmware < 1.9.1; Phoenix Contact CHARX SEC-3100 Firmware < 1.9.1; Phoenix Contact CHARX SEC-3150 Firmware < 1.9.1.
- Is there a fix for CVE-2026-44103?
- A patch was published on 2026-07-30: Fixed in firmware version 1.9.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44103 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44103?
- 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 Phoenix Contact CHARX SEC-3xxx series charging controllers contain a vulnerability in the JupiCore service. The service fails to perform integrity or verification checks (such as cryptographic signatures) on firmware updates transmitted to the internal charging module. An unauthenticated remote attacker can exploit this lack of verification to inject and execute malicious firmware. This vulnerability can be chained with other flaws, such as CVE-2026-44104, to further compromise the device. The issue is resolved in firmware version 1.9.1.
Affected products
- Phoenix Contact CHARX SEC-3000 Firmware < 1.9.1
- Phoenix Contact CHARX SEC-3050 Firmware < 1.9.1
- Phoenix Contact CHARX SEC-3100 Firmware < 1.9.1
- Phoenix Contact CHARX SEC-3150 Firmware < 1.9.1
Timeline
- 2026-07-30: disclosed
- 2026-07-30: advisory
- 2026-07-30: patched: Fixed in firmware version 1.9.1