dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-11917

HIGH · 7.2 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 →
78/100
Remediation priority · High
Remotely reachable Zero-click 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 Rockwell Automation ThinManager® software due to improper limitation of file save operations within the API. An authenticated attacker could exploit this vulnerability to write arbitrary files to restricted system directories outside of the application's intended directory.

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

This is a path traversal vulnerability in Rockwell Automation ThinManager's API where improper limitation of file save operations allows an authenticated attacker to write arbitrary files to restricted system directories outside the application's intended directory. The issue stems from insufficient input validation on file path parameters in the file save functionality.

MitigationImplement strict path validation and canonicalization in the affected API endpoints to ensure resolved file paths remain within the application's designated directory boundaries. Restrict file write operations to explicitly allowed paths.

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
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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. Identify ThinManager installation
    Search for ThinManager installation directories (commonly at C:\Program Files\Rockwell Software\ThinManager or C:\Program Files (x86)\ThinManager) and locate the ThinManager.exe or related executable files
    Affected if ThinManager software is found on the system
  2. Determine ThinManager version
    Right-click ThinManager.exe, select Properties, and check the Version tab; or run 'ThinManager.exe /?' or check the About dialog within the application
    Affected if Installed version falls within the affected version range (compare against vendor advisory)
  3. Verify API service status
    Check if ThinManager's web API service is running by examining running services (services.msc) or checking for listening ports (typically 80/443 or custom API ports via netstat -an | findstr LISTENING)
    Affected if API service is running and accepting connections
  4. Confirm authenticated access to file save API
    Review ThinManager configuration files (typically in the config directory) for API authentication settings; check if the file save endpoint (look for endpoints handling file upload/save operations) allows authenticated user access
    Affected if File save API endpoint is accessible to authenticated users without additional restrictions
  5. Inspect file path validation in API configuration
    Examine ThinManager's API configuration files and logs for evidence of path traversal protections; check web.config or similar config files for input validation settings related to file operations
    Affected if File save functionality lacks proper path validation or canonicalization as documented in the vulnerability description

Your environment is affected if ThinManager is installed with the API enabled, the file save endpoint is accessible to authenticated users, and the installed version is within the affected range without path validation controls in place.

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

Implement strict path validation and canonicalization in the affected API endpoints to ensure resolved file paths remain within the application's designated directory boundaries. Restrict file write operations to explicitly allowed paths.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11917 — 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-11917 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