Malicious firmware injection via unchecked JupiCore transfer
Published Jul 30, 2026 · Updated Jul 30, 2026
Unrestricted firmware upload in Phoenix Contact CHARX SEC-3xxx before 1.9.1 allows remote attackers to alter charging-module firmware. The JupiCore service forwards attacker-supplied firmware to the internal charging module without performing integrity validation or verification. No authentication or user interaction is required, but the published impact is limited to device integrity unless the flaw is chained with another vulnerability.
Summary
What happened
Unrestricted firmware upload in Phoenix Contact CHARX SEC-3xxx before 1.9.1 allows remote attackers to alter charging-module firmware. The JupiCore service forwards attacker-supplied firmware to the internal charging module without performing integrity validation or verification. No authentication or user interaction is required, but the published impact is limited to device integrity unless the flaw is chained with another vulnerability.
The record
- CVE
- CVE-2026-44103
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-434, T0857
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.9.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo