dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-9108

MEDIUM · 5.4 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
54/100
Remediation priority · Moderate
5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A path traversal security issue exists within Studio 5000 Logix Designer® due to improper limitation of file paths within ACD project files. The software does not sanitize or validate file names embedded in the ACD file structure during the project opening procedure, allowing path traversal sequences to escape the intended extraction directory. If exploited, an attacker could craft a malicious ACD project file that results in arbitrary files being written to attacker-controlled locations on the file system, potentially leading to code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Studio 5000 Logix Designer fails to sanitize or validate file names embedded in ACD project files during the project opening procedure. This allows path traversal sequences (e.g., ../../../') to escape the intended extraction directory, enabling arbitrary file writes to attacker-controlled locations on the file system, which could lead to code execution.

MitigationOrganizations should avoid opening untrusted or unknown ACD project files in Studio 5000 Logix Designer until Rockwell Automation releases an official patch. Implement file origin and integrity verification processes for all ACD files before opening.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Studio 5000 Logix Designer is installed
    Check for the application in the Windows Program Files directory, typically under Rockwell Automation or check via Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries named 'Studio 5000 Logix Designer'
    Affected if The application is present on the system
  2. Determine the installed version of Studio 5000 Logix Designer
    Open the application and navigate to Help > About, or check the file version of the main executable (typically RSLogix5000.exe or LogixDesigner.exe in the installation directory) by right-clicking and selecting Properties > Details
    Affected if The version number falls within any affected range that may be published by Rockwell Automation for this CVE
  3. Identify ACD project files on the system
    Search the file system for files with the .acd extension using the command: Get-ChildItem -Path C:\ -Recurse -Filter *.acd -ErrorAction SilentlyContinue | Select-Object -First 20 FullName
    Affected if ACD project files exist and could be opened by the application
  4. Check recent project file access activity
    Review Windows Event Logs under Security or Application logs for recent instances of Studio 5000 opening .acd files, or check the application's recent projects list if accessible
    Affected if Users have recently opened ACD files, indicating active use of the vulnerable functionality
  5. Assess source of ACD files
    Examine the origin and acquisition method of any ACD files present: check if they were received from external sources, downloaded from the internet, or obtained from untrusted vendors
    Affected if ACD files originate from untrusted or unknown sources, increasing the risk of encountering a malicious file

You are affected if Studio 5000 Logix Designer is installed and you open or have opened ACD project files, particularly those from untrusted sources, as the vulnerability triggers during the project opening procedure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should avoid opening untrusted or unknown ACD project files in Studio 5000 Logix Designer until Rockwell Automation releases an official patch. Implement file origin and integrity verification processes for all ACD files before opening.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9108 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data