CVE-2026-103975 in Appium
Summary
by MITRE • 10/14/2026
Appium is a cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol. Prior to 7.2.6, @appium/support ZIP extraction accepts an archive entry that creates a symbolic link to a location outside the extraction directory and then accepts a later regular-file entry whose legitimate name resolves through that link. The lexical containment check examines entry names without validating the symlink target or the real destination, so an attacker-controlled archive can write files to arbitrary locations writable by the Appium process. This is distinct from the earlier parent-directory entry-name traversal fixed in 7.0.6 because the bypass uses no parent-directory or absolute entry name. Depending on the writable destination, the arbitrary file write can overwrite configuration, startup scripts, or executables and lead to code execution. This issue is fixed in version 7.2.6.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 10/14/2026
The vulnerability identified as a path traversal flaw within the Appium support library allows for unauthorized arbitrary file writes through a sophisticated manipulation of ZIP archive structures. Appium serves as a critical cross-platform automation framework built upon the W3C WebDriver protocol, widely used by developers and QA engineers to test mobile applications on iOS and Android devices. The core technical deficiency resides in the zip extraction logic within versions prior to 7.2.6, specifically in how it handles symbolic links during the decompression process. When processing a maliciously crafted ZIP archive, the extractor fails to validate the target of symbolic link entries against the intended extraction directory. This oversight permits an attacker-controlled archive to first introduce a symbolic link entry that points to a location outside the designated safe zone, followed by a regular file entry whose name resolves through this symlink. Consequently, files are written to arbitrary locations on the host system where the Appium process has write permissions, bypassing standard containment checks that typically rely solely on lexical analysis of entry names without verifying the actual filesystem destination via real path resolution.
This specific attack vector is distinct from traditional directory traversal vulnerabilities because it does not utilize parent-directory sequences such as dot-dot-slash or absolute paths to escape the extraction root. Instead, it exploits the operating system's handling of symbolic links during file creation operations. By leveraging this mechanism, an attacker can overwrite critical configuration files, startup scripts, or executable binaries located in directories accessible by the Appium process. The operational impact is severe, as overwriting these components can lead to remote code execution on the host machine running the automation framework. This poses a significant risk particularly in continuous integration and deployment pipelines where automated tests are executed with elevated privileges or access to sensitive system resources. An attacker could potentially compromise the integrity of the testing environment, steal credentials stored in configuration files, or establish persistence by modifying startup scripts.
From a classification perspective, this vulnerability aligns with CWE-22 Improper Limitation of a Pathname to a Restricted Directory and CWE-59 Improper Link Resolution Before File Access Symlink Race Condition, as it involves the misuse of symbolic links to bypass access controls. In terms of offensive security tactics, this technique corresponds to ATT&CK T1036 Masquerading or potentially T1482 Domain Trust Discovery if used in broader attack chains, though primarily it represents a file manipulation tactic under T1553 Subvert Trust Controls by modifying system files. The mitigation strategy is straightforward and has already been implemented in the latest release of the software. Users must upgrade to Appium version 7.2.6 or later, which includes enhanced validation logic that resolves symbolic links before writing files, ensuring that all extracted content remains strictly within the intended extraction directory regardless of symlink targets. Until this update is applied, organizations should restrict file write permissions for the Appium process and avoid processing untrusted ZIP archives to mitigate the risk of arbitrary code execution.