CVE-2024-26000: PHOENIX CONTACT: Out of bounds read only memory access
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.81% (FIRST EPSS); higher than 57.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 12, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-125
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · CERTVDE
- 5.9
- 1.6 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | charx sec-3000 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware |
| phoenixcontact | charx sec-3000 | cpe:2.3:h:phoenixcontact:charx_sec-3000 |
| phoenixcontact | charx sec-3050 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware |
| phoenixcontact | charx sec-3050 | cpe:2.3:h:phoenixcontact:charx_sec-3050 |
| phoenixcontact | charx sec-3100 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware |
| phoenixcontact | charx sec-3100 | cpe:2.3:h:phoenixcontact:charx_sec-3100 |
| phoenixcontact | charx sec-3150 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware |
| phoenixcontact | charx sec-3150 | cpe:2.3:h:phoenixcontact:charx_sec-3150 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
PHOENIX CONTACT CHARX SEC-3000
- up to and including 1.5.0affected · semver
PHOENIX CONTACT CHARX SEC-3050
- up to and including 1.5.0affected · semver
PHOENIX CONTACT CHARX SEC-3100
- up to and including 1.5.0affected · semver
PHOENIX CONTACT CHARX SEC-3150
- up to and including 1.5.0affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact charx sec-3000 firmwarebefore 1.5.1
- phoenixcontact charx sec-3050 firmwarebefore 1.5.1
- phoenixcontact charx sec-3100 firmwarebefore 1.5.1
- phoenixcontact charx sec-3150 firmwarebefore 1.5.1
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-25270Remote Code Execution via Unauthenticated Configuration Manipulation39Monitor
- CVE-2024-6788Phoenix Contact: update feature from CHARX controller can be used to reset a low privilege user password39Monitor
- CVE-2024-26001PHOENIX CONTACT: Out of bounds write only memory access39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-25998Mar 12, 2024 · PHOENIX CONTACT: Command injection in the OCPP Service29Monitor
- ← EarlierCVE-2024-25999Mar 12, 2024 · PHOENIX CONTACT: Privilege escalation in the OCPP agent service31Monitor
- Later →CVE-2024-26002Mar 12, 2024 · PHOENIX CONTACT: File ownership manipulation in CHARX Series31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Peter Geisslerfinder
- Rick De Jagerfinder
- Carlo Meijerfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-260030 days apartPHOENIX CONTACT: DoS of the control agent in CHARX Series30Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.