Arbitrary file write via unsanitized ACD paths
Published Jul 14, 2026 · Updated Jul 14, 2026
Path traversal in ACD handling in Rockwell Automation Studio 5000 Logix Designer allows local users to write arbitrary files via a crafted project. The project-opening routine neither sanitizes nor validates embedded file names before extraction, so traversal sequences escape the intended directory. Exploitation requires low-privileged local access and user interaction; attacker-chosen file writes can lead to code execution.
Summary
What happened
Path traversal in ACD handling in Rockwell Automation Studio 5000 Logix Designer allows local users to write arbitrary files via a crafted project. The project-opening routine neither sanitizes nor validates embedded file names before extraction, so traversal sequences escape the intended directory. Exploitation requires low-privileged local access and user interaction; attacker-chosen file writes can lead to code execution.
The record
- CVE
- CVE-2026-9108
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Rockwell Automation
- Product
- Studio 5000 Logix Designer
- Classifications
- CWE-22, CAPEC-126, T1203, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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=V36.00, 35.00,35.01, 34.00-34.03, 33.00-33.03, 32.00-32.04 and older
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