Firmware compromise via CRC32-only update validation
Published Jul 30, 2026 · Updated Jul 30, 2026
Improper firmware verification in Phoenix Contact CHARX SEC-3xxx before 1.9.1 allows remote attackers to install modified firmware. CharxControllerAgent accepts a basemodule update after checking only its CRC32 checksum and does not authenticate the image with a cryptographic signature. No authentication is required, and a crafted image can replace trusted firmware and compromise the controller; arbitrary-code execution is reported when the flaw is chained with other vulnerabilities.
Summary
What happened
Improper firmware verification in Phoenix Contact CHARX SEC-3xxx before 1.9.1 allows remote attackers to install modified firmware. CharxControllerAgent accepts a basemodule update after checking only its CRC32 checksum and does not authenticate the image with a cryptographic signature. No authentication is required, and a crafted image can replace trusted firmware and compromise the controller; arbitrary-code execution is reported when the flaw is chained with other vulnerabilities.
The record
- CVE
- CVE-2026-44104
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-347, T1495
- 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