Quick answers
- Is CVE-2026-44105 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44105 being exploited in the wild.
- How severe is CVE-2026-44105?
- Medium severity, with a CVSS score of 6.6, published 30 July 2026.
- Which products and versions are affected?
- Phoenix Contact CHARX SEC-3000 1.0.0 to 1.9.0; Phoenix Contact CHARX SEC-3050 1.0.0 to 1.9.0; Phoenix Contact CHARX SEC-3100 1.0.0 to 1.9.0; Phoenix Contact CHARX SEC-3150 1.0.0 to 1.9.0.
- Is there a fix for CVE-2026-44105?
- 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-44105 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-44105?
- 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
This vulnerability is classified as an insertion of sensitive information into log files (CWE-532). The firmware for CHARX SEC-3xxx charging controllers incorrectly writes the credentials for the 'user-app' account into system logs. A local attacker with low-privileged access to the file system or log services can retrieve these credentials to authenticate via SSH as the 'user-app' user. This level of access can be used to interrupt charging services or as a stepping stone for further privilege escalation. The issue is resolved in firmware version 1.9.1.
Affected products
- Phoenix Contact CHARX SEC-3000 1.0.0 to 1.9.0
- Phoenix Contact CHARX SEC-3050 1.0.0 to 1.9.0
- Phoenix Contact CHARX SEC-3100 1.0.0 to 1.9.0
- Phoenix Contact CHARX SEC-3150 1.0.0 to 1.9.0
Timeline
- 2026-07-30: disclosed
- 2026-07-30: advisory