Skip to content
Fencer Intel
high 7.5

CVE-2024-26003 json

PHOENIX CONTACT: DoS of the control agent in CHARX Series

published 2y ago modified 4mo ago also EUVD-2024-23299

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

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

Patch / fix

  • phoenixcontact charx_sec-3000_firmware 1.5.1
  • phoenixcontact charx_sec-3050_firmware 1.5.1
  • phoenixcontact charx_sec-3100_firmware 1.5.1
  • phoenixcontact charx_sec-3150_firmware 1.5.1

Is CVE-2024-26003 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

1.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • PHOENIX CONTACT CHARX SEC-3000
  • PHOENIX CONTACT CHARX SEC-3050
  • PHOENIX CONTACT CHARX SEC-3100
  • PHOENIX CONTACT CHARX SEC-3150
  • phoenixcontact charx_sec_3000
  • phoenixcontact charx_sec_3050
  • phoenixcontact charx_sec_3100
  • phoenixcontact charx_sec_3150

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.