CVE-2024-26003

CVE-2024-26003 is a high-severity vulnerability in Phoenixcontact Charx Sec-3000 Firmware with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-125.

Key facts

Description

An unauthenticated remote attacker can DoS the control agent due to a out-of-bounds read which may prevent or disrupt the charging functionality.

Frequently asked questions

What is CVE-2024-26003?
An unauthenticated remote attacker can DoS the control agent due to a out-of-bounds read which may prevent or disrupt the charging functionality.
How severe is CVE-2024-26003?
CVE-2024-26003 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2024-26003 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-26003?
CVE-2024-26003 primarily affects Phoenixcontact Charx Sec-3000 Firmware. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-26003?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-26003 have an EU (EUVD) identifier?
Yes. CVE-2024-26003 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-23299.
When was CVE-2024-26003 published?
CVE-2024-26003 was published on 2024-03-12 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Phoenixcontact Charx Sec-3000 Firmware

All CVEs affecting Phoenixcontact Charx Sec-3000 Firmware →

Other CWE-125 (Out-of-bounds Read) vulnerabilities

Browse all CWE-125 (Out-of-bounds Read) vulnerabilities →