Code execution via crafted-file stack overflow
Published Aug 5, 2025 · Updated Feb 26, 2026
Stack-based buffer overflow in Rockwell Automation Arena Simulation 16.20.09 and earlier allows attackers to execute code via a crafted file. The file-processing code reads and writes past the end of a stack buffer when it handles malicious content, but Rockwell Automation has not identified the affected parser or file format. Exploitation requires a user to open the file or a malicious webpage and can execute code or disclose information in the Arena process.
Summary
What happened
Stack-based buffer overflow in Rockwell Automation Arena Simulation 16.20.09 and earlier allows attackers to execute code via a crafted file. The file-processing code reads and writes past the end of a stack buffer when it handles malicious content, but Rockwell Automation has not identified the affected parser or file format. Exploitation requires a user to open the file or a malicious webpage and can execute code or disclose information in the Arena process.
The record
- CVE
- CVE-2025-7032
- Published
- Aug 5, 2025
- Updated
- Feb 26, 2026
- Vendor
- Rockwell Automation
- Product
- Arena Simulation
- Classifications
- CWE-121, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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=16.20.09 and prior
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