CVE-2026-44104
Deferred Deferred - Pending Action

BaseFortify

Publication date: 2026-07-30

Last updated on: 2026-07-30

Assigner: CERT VDE

Description
The firmware update process for the basemodule of the charging controller only validates the CRC32 checksum without cryptographic signature verification. This allows an unauthenticated remote attacker to install a modified firmware, resulting in full system compromise.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-30
Last Modified
2026-07-30
Generated
2026-10-19
AI Q&A
2026-07-30
EPSS Evaluated
2026-10-18
NVD
CVE-2026-44104
EUVD
EUVD-2026-51039

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
Phoenix Contact CHARX SEC-3150 1.0.0
Phoenix Contact CHARX SEC-3100 1.0.0
Phoenix Contact CHARX SEC-3050 1.0.0
Phoenix Contact CHARX SEC-3000 1.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-347 The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves the firmware update process for the basemodule of a charging controller. It only checks the CRC32 checksum and does not verify cryptographic signatures. This allows an unauthenticated remote attacker to install malicious firmware, leading to full system compromise.

Detection Guidance

Detecting this vulnerability requires checking if firmware updates are validated only by CRC32 checksums without cryptographic signatures. Monitor network traffic for unauthorized firmware update requests or unexpected firmware installations. Inspect system logs for anomalies during firmware update processes.

Impact Analysis

An attacker could exploit this to install unauthorized firmware, gaining control over the charging controller system. This could disrupt operations, steal sensitive data, or cause physical damage depending on the system's use case.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, violating compliance requirements such as GDPR or HIPAA. Organizations may face legal penalties, loss of certification, or reputational damage due to insufficient security controls.

Mitigation Strategies

Immediately disable unauthenticated firmware updates if possible. Implement cryptographic signature verification for all firmware updates. Restrict network access to firmware update servers to trusted sources only. Update firmware to a patched version if available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44104. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart