CODESYS Control RTE (SL): Incorrect Authorization
CVE-2026-8046 is a high-severity incorrect authorization vulnerability in CODESYS Control RTE (SL) from Codesys, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 3.5.22.20 as the first without the flaw, so updating CODESYS Control RTE (SL) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.35% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update CODESYS Control RTE (SL) to 3.5.22.20 or a later version.
- Update CODESYS Control RTE (for Beckhoff CX) SL to 3.5.22.20 or a later version.
- Update CODESYS Control Win (SL) to 3.5.22.20 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| CODESYS | CODESYS Control RTE (SL) | 3.0.0.0 up to, but not including, 3.5.22.20 | 3.5.22.20 |
| CODESYS | CODESYS Control RTE (for Beckhoff CX) SL | 3.0.0.0 up to, but not including, 3.5.22.20 | 3.5.22.20 |
| CODESYS | CODESYS Control Win (SL) | 3.0.0.0 up to, but not including, 3.5.22.20 | 3.5.22.20 |
| CODESYS | CODESYS HMI (SL) | 3.0.0.0 up to, but not including, 3.5.22.20 | 3.5.22.20 |
| CODESYS | CODESYS Runtime Toolkit | 3.0.0.0 up to, but not including, 3.5.22.20 | 3.5.22.20 |
| CODESYS | CODESYS Control for BeagleBone SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for emPC-A/iMX6 SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for IOT2000 SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for Linux ARM SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for Linux SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for PFC100 SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for PFC200 SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for PLCnext SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for Raspberry Pi SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Control for WAGO Touch Panels 600 SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
| CODESYS | CODESYS Virtual Control SL | 3.0.0.0 up to, but not including, 4.21.0.0 | 4.21.0.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by CNA (cert.vde.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.2 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 8.1 | High | CNA (cert.vde.com) |
Official description
The affected products insufficiently verify authorization when deleting user accounts. An authenticated, low-privileged remote user can exploit this vulnerability to delete other users, including those with higher privileges.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in CODESYS Control RTE (SL)
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
Recent Incorrect Authorization vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 7.1 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.