dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-58192

HIGH · 8.6 CVSS v3.1 Published 2026-07-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 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
Appium is a cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol. Prior to 1.1.6, the Appium storage plugin exposes POST /storage/delete, whose handler passes the user-supplied name value directly into path.join(storageRoot, name) and fs.rimraf() without path sanitization, allowing an unauthenticated remote client to escape the storage root with ../ sequences and recursively delete arbitrary writable files or directories. This issue is fixed in version 1.1.6.

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

The Appium storage plugin prior to version 1.1.6 contains a path traversal vulnerability in the POST /storage/delete endpoint. The handler passes the user-supplied 'name' parameter directly into path.join() and fs.rimraf() without sanitization, allowing unauthenticated remote attackers to escape the configured storage root directory using ../ sequences and recursively delete arbitrary writable files or directories on the host system.

MitigationUpgrade to Appium version 1.1.6 or later. If immediate upgrade is not feasible, disable or restrict access to the storage plugin endpoint and implement input validation to reject path traversal sequences (../) in user-supplied filenames.

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
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

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 Appium installation and version
    Run 'appium --version' or check the package.json file for the 'appium' or '@appium/base-plugin' version entry
    Affected if The installed version is below 1.1.6 (or the version cannot be determined and the storage plugin is present)
  2. Locate the storage plugin
    Run 'npm list @appium/storage-plugin' or search for the storage plugin in node_modules and package.json dependencies
    Affected if The storage plugin package is installed (regardless of version, as version detection may be incomplete)
  3. Check storage plugin version
    Run 'npm list @appium/storage-plugin' to see the installed version, or inspect the plugin's package.json file in node_modules
    Affected if The storage plugin version is present and below 1.1.6
  4. Verify storage root directory configuration
    Check Appium server logs, configuration files (appium.config.js, appium.yaml), or environment variables for 'storageRoot' or similar storage path settings
    Affected if A storage root directory is configured and the plugin is in use (the vulnerability allows escaping this configured root)
  5. Confirm endpoint accessibility
    Attempt a local HTTP request to POST /storage/delete (e.g., curl -X POST http://localhost:4723/storage/delete -d 'name=test') or check network exposure of the Appium server
    Affected if The Appium server with storage plugin is network-accessible (the vulnerability is exploitable by unauthenticated remote attackers)

A user is affected if the Appium storage plugin is installed and its version is below 1.1.6, with the /storage/delete endpoint exposed and a storage root configured.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Appium version 1.1.6 or later. If immediate upgrade is not feasible, disable or restrict access to the storage plugin endpoint and implement input validation to reject path traversal sequences (../) in user-supplied filenames.

Recommended fix High confidence

Appium version 1.1.6 or later

  1. 1. Identify the current Appium version by running `appium --version` or checking package.json
  2. 2. If the current version is prior to 1.1.6, upgrade Appium to version 1.1.6 or later using the appropriate package manager (e.g., `npm install -g [email protected]` or `pip install Appium-Python-Client` upgrade method)
  3. 3. Verify the upgrade was successful by checking the new version
  4. 4. Restart the Appium server to ensure the patched code is loaded
  5. 5. Test that the /storage/delete endpoint now properly sanitizes path inputs and rejects ../ sequences
Caveat No breaking changes specifically documented for this security patch; this is a point release fix

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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