CVE-2026-3509
Last modified
CVE-2026-3509 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. An unauthenticated remote attacker may be able to control the format string of messages processed by the Audit Log of the CODESYS Control runtime system, potentially resulting in a denial‑of‑service (DoS) condition.. EPSS estimates a 0.35% chance of exploitation in the next 30 days.
Description
An unauthenticated remote attacker may be able to control the format string of messages processed by the Audit Log of the CODESYS Control runtime system, potentially resulting in a denial‑of‑service (DoS) condition.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| CODESYS | CODESYS Control RTE (SL) | >= 3.5.17.0, < 3.5.22.0 |
| CODESYS | CODESYS Control RTE (for Beckhoff CX) SL | >= 3.5.17.0, < 3.5.22.0 |
| CODESYS | CODESYS Control Win (SL) | >= 3.5.17.0, < 3.5.22.0 |
| CODESYS | CODESYS Runtime Toolkit | >= 3.5.17.0, < 3.5.22.0 |
| CODESYS | CODESYS Control for BeagleBone SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for emPC-A/iMX6 SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for IOT2000 SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for Linux ARM SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for Linux SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for PFC100 SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for PFC200 SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for PLCnext SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for Raspberry Pi SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Control for WAGO Touch Panels 600 SL | >= 4.1.0.0, < 4.21.0.0 |
| CODESYS | CODESYS Virtual Control SL | >= 4.1.0.0, < 4.21.0.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-3509?
How severe is CVE-2026-3509?
How do I fix CVE-2026-3509?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-35083A remote attacker with user privileges can exploit a stack b…8.8
- CVE-2026-35084A remote attacker with user privileges can exploit a stack b…8.8
- CVE-2026-35085A remote attacker with user privileges can exploit a stack b…8.8
- CVE-2026-35086Improper Control of Generation of Code ('Code Injection') vu…6.5
- CVE-2026-35087Slican telephone exchanges allow administrative protocol aut…9.3
- CVE-2026-35089In Slican telephone exchanges secure key is generated in a p…8.7
- CVE-2026-35090In Slican telephone exchanges it is possible to manage the c…9.3
- CVE-2026-35091A flaw was found in Corosync. A remote unauthenticated attac…8.2
- CVE-2026-35092A flaw was found in Corosync. An integer overflow vulnerabil…7.5
- CVE-2026-35093A flaw was found in libinput. A local attacker who can place…8.8
- CVE-2026-35094A flaw was found in libinput. An attacker capable of deployi…5.5
- CVE-2026-35095KTM System e-BOK allows the session identifier to be set by …4.8
Are you affected by CVE-2026-3509?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST