CVE-2022-45792 is a high severity (CVSS 7.8) path traversal flaw in Omron Sysmac Studio, the engineering software used to program Omron controllers. A malicious project file can cause the software to write files outside the intended location. The record gives no fixed version, so check the vendor advisory.
What's affected
The NVD record lists Omron Sysmac Studio with no version range, so you cannot tell from the record alone which releases are affected. The weakness is in how the software handles project files. It runs with the privileges of the logged-in user, so the damage is bounded by what that account can write.
The Dragos advisory that the record cites groups this CVE with other Omron PLC and engineering software issues. It was published on 22 January 2024 in NVD. I could not confirm a fixed version from the pages available, so treat the vendor's own bulletin as the source of truth.
How to check if you're exposed
This is desktop software, so there is no package to query. Open Sysmac Studio, go to the Help menu and read the About dialog for the installed version. Then compare it with Omron's security bulletins for Sysmac Studio, and with the Dragos advisory listed under Sources.
Also list where project files come from. Any engineering workstation that opens project files received by email, shared drives or vendor portals is in scope for this weakness.
What to do now
- Find every machine with Sysmac Studio installed, including laptops that engineers take to the plant floor.
- Compare each version against the vendor advisory and update to the release it names as fixed.
- Open project files only from sources you trust. Treat a file from an unknown sender the way you would treat an unknown executable.
- Run the software as a standard user, not an administrator, so a bad write cannot reach system locations.
- Keep engineering workstations on a separate network segment from general office machines.
Why it matters
The weakness class is CWE-22, improper limitation of a pathname to a restricted directory. A project file carries names for the files the software should create. If the software does not check that those names stay inside the project folder, a crafted name can point elsewhere and overwrite a file the user can write to.
The attack vector in the record is local with low complexity and no privileges beyond a normal account, and it needs a user to open the file. That makes the realistic risk a poisoned project file passed between people. The record does not flag this CVE as exploited in the wild and CISA's KEV flag is false.
Quick check
Is CVE-2022-45792 exploited in the wild?
The record's KEV flag is false and I found no advisory that says it is exploited. That is not proof of safety, only the current state of the public record.
Does it need network access?
No. The vector is local. An attacker needs a way to get a malicious project file opened on a workstation.
Sources
- NVD record for CVE-2022-45792
- Dragos advisory on Omron PLC and engineering software
- Gold page for CVE-2022-45792
You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.
Last reviewed: 19 October 2026.