Unauthenticated code execution via check_account stack overflow
Published Dec 10, 2025 · Updated Dec 10, 2025
Stack-based buffer overflow in WAGO Industrial Managed Switches before 02.64 allows remote attackers to execute code without authentication. The lighttpd check_account() parser passes attacker-controlled HTTP fields to unsafe sscanf calls that write beyond fixed-size stack buffers. No account or user interaction is required; successful corruption enables arbitrary code execution, while failed attempts can disable the web interface until manual recovery.
Summary
What happened
Stack-based buffer overflow in WAGO Industrial Managed Switches before 02.64 allows remote attackers to execute code without authentication. The lighttpd check_account() parser passes attacker-controlled HTTP fields to unsafe sscanf calls that write beyond fixed-size stack buffers. No account or user interaction is required; successful corruption enables arbitrary code execution, while failed attempts can disable the web interface until manual recovery.
The record
- CVE
- CVE-2025-41730
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- WAGO
- Product
- Industrial Managed Switches
- Classifications
- CWE-787, CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <02.64
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo