CVE-2026-76992
Uncontrolled Memory Allocation in CODESYS Gateway Client
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.5.22.40, 4.23.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The CODESYS Gateway Client allocates memory based on a size field in a gateway response without enforcing an appropriate upper limit. An unauthenticated remote attacker controlling a malicious gateway can exploit this behavior to trigger excessive memory consumption, resulting in a denial-of-service condition thus leading to a total loss of availablity.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- CODESYS Development System 3
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS Gateway
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS Edge Gateway for Windows
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS HMI (SL)
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS OPC DA Server SL
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS PLCHandler
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS Runtime Toolkit
From 3.0.0.0 · fixed in 3.5.22.40
- CODESYS Edge Gateway for Linux
From 3.15.0.0 · fixed in 4.23.0.0