Quick answers
- Is CVE-2026-44107 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44107 being exploited in the wild.
- How severe is CVE-2026-44107?
- High severity, with a CVSS score of 7.5, published 30 July 2026.
- Which products and versions are affected?
- Phoenix Contact CHARX SEC-3000 1.0.0 to 1.9.1 (exclusive); Phoenix Contact CHARX SEC-3050 1.0.0 to 1.9.1 (exclusive); Phoenix Contact CHARX SEC-3100 1.0.0 to 1.9.1 (exclusive); Phoenix Contact CHARX SEC-3150 1.0.0 to 1.9.1 (exclusive).
- Is there a fix for CVE-2026-44107?
- 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-44107 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-44107?
- 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 CharxModbusServer component in Phoenix Contact CHARX SEC-3xxx charging controllers exposes a dangerous method or function via Modbus TCP. An unauthenticated remote attacker can send a specific Modbus command to the listening port to trigger a system reboot. This vulnerability (CWE-749) is accessible whenever Modbus functionality is enabled and the port is reachable over the network. Successful exploitation results in a Denial-of-Service (DoS) condition. The issue is addressed in firmware version 1.9.1.
Affected products
- Phoenix Contact CHARX SEC-3000 1.0.0 to 1.9.1 (exclusive)
- Phoenix Contact CHARX SEC-3050 1.0.0 to 1.9.1 (exclusive)
- Phoenix Contact CHARX SEC-3100 1.0.0 to 1.9.1 (exclusive)
- Phoenix Contact CHARX SEC-3150 1.0.0 to 1.9.1 (exclusive)
Timeline
- 2026-07-30: disclosed
- 2026-07-30: advisory
- 2026-07-30: patched: Fixed in firmware version 1.9.1