Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The npm package @appium/support, before version 7.2.6, does not check symbolic link targets when extracting ZIP archives, so files can be written outside the extraction directory. An attacker who can supply an archive that Appium extracts can combine a symlink entry with a later file entry to write to any location the Appium process can write, possibly leading to code execution. Upgrade @appium/support to version 7.2.6, which contains the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0064, the 50th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:33 UTC First seen by agentprime
- 31 Oct 2026, 13:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qfxx-c367-67f8
- OSV: GHSA-qfxx-c367-67f8
- github.com/appium/appium/security/advisories/GHSA-qfxx-c367-67f8
- nvd.nist.gov/vuln/detail/CVE-2026-103975
- github.com/appium/appium/pull/22436
- github.com/appium/appium/commit/d9eb36f413153e28b04b92d8ce4447da270371c0
- github.com/appium/appium
- github.com/appium/appium/releases/tag/@appium/[email protected]