Skip to content
Fencer Intel
medium 5.9

CVE-2024-26000 json

PHOENIX CONTACT: Out of bounds read only memory access

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

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

Summary

An unauthenticated remote attacker can read memory out of bounds due to improper input validation in the MQTT stack. The brute force attack is not always successful because of memory randomization.

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-26000 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
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

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

CVSS scores

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

Affected products

  • PHOENIX CONTACT CHARX SEC-3000
  • PHOENIX CONTACT CHARX SEC-3050
  • PHOENIX CONTACT CHARX SEC-3100
  • PHOENIX CONTACT 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.