ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-103975

Appium is a cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol.

Published Oct 14, 2026 · catalog updated Oct 15, 2026 · Appium is a cross-platform

Check if you run it

No confirmed exploitation is on record for CVE-2026-103975. EPSS is 0.65%. Act only if a listed version of Appium is a cross-platform is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Appium is a cross-platform).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.65%
Remediation
Version ranges on file
Affected products
npm @appium · npm @appium/support

### Summary CVE-2026-30973 [(GHSA-rfx7-4xw3-gh4m)](https://github.com/appium/appium/security/advisories/GHSA-rfx7-4xw3-gh4m) was a plain path traversal in the entry name. The containment check built an Error object without throwing it, so an entry literally named something like was written outside the destination. That issue was fixed in @appium/support 7.0.6 by actually rejecting out of bound entry names. This finding is a different vector that the 7.0.6 fix does not cover. The archive entry names here are completely legitimate (for example and , no anywhere), so every name based defense accepts them. The escape happens through a symbolic link. One entry is a symlink whose target points outside the extraction directory, and a later entry is a regular file whose name resolves through that symlink. The name based containment check never inspects the symlink target, and the extractor writes the symlink target verbatim, so the file lands outside the extraction root. The two issues compared on the same patched version 7.2.5: | | CVE-2026-30973 | This finding | |---|---|---| | Vector | one entry whose name contains | a symlink entry plus a file written through it | | Entry names | contain (illegal) | legitimate, no and not absolute | | What is missing | the name chec\k did not throw | name checks never resolve symlinks, and the symlink target is unchecked | | Entries needed | one | two | | Fixed in 7.0.6 | yes | no | | Status on 7.2.5 | blocked | still exploitable (proven below) | ### Details ## Root cause The extractor applies only a lexical containment check on each entry's own name, then for a symlink entry it creates the link with the target taken straight from the archive: compares normalized strings and does not call realpath, so for the file entry the destination is lexically inside and the check passes, even though is a symlink created by the previous entry that points outside . The write then follows that symlink and escapes. The symlink target itself is never v

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @appiumversion unspecified
  • npm @appium/support0 → 7.2.6
  • npm @appium/support<7.2.6
  • npm @appium/support<= 7.2.5

How to fix CVE-2026-103975

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-103975. EPSS is 0.65%. Act only if a listed version of Appium is a cross-platform is installed.

Which versions are affected?

Compare what you have installed with 0 → 7.2.6, <7.2.6, <= 7.2.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-59: Link Following. EPSS 0.65%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · NIST NVD

    Detected

    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 entr

  2. Oct 15, 2026 · NIST NVD

    Updated

    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 entr

  3. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    @appium/support fixed in 7.2.6

  4. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    @appium/support fixed in 7.2.6

  5. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ### Summary CVE-2026-30973 [(GHSA-rfx7-4xw3-gh4m)](https://github.com/appium/appium/security/advisories/GHSA-rfx7-4xw3-gh4m) was a plain path traversal in the entry name. The containment check built an Error object without throwing it, so an entry literally named something like was written outside the destination. That issue was fixed in @appium/support 7.0.6 by actually rejecting out of bound ent

Sources

  • CVE.orgVulnerability recordCVE-2026-103975

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-103975

    30-day exploitation probability 0.6%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-qfxx-c367-67f8

    Appium: Symlink based Zip Slip in @appium/support ZIP extraction

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-103975

    CVE-2026-30973 (GHSA-rfx7-4xw3-gh4m) was a plain path traversal in the entry name. The containment check built an Error object without throwing it, so an entry literally named something like ../evil.txt was written outside the destination. That issue was fixed in @appium/support 7.0.6 by actually rejecting out of bound entry names. This finding is a different vector that the 7.0.6 fix does not cov

    advisories.gitlab.com
  • GitLab Advisory DatabasePackage advisorynpm/@appium/support/CVE-2026-103975.yml

    CVE-2026-30973 [(GHSA-rfx7-4xw3-gh4m)](https://github.com/appium/appium/security/advisories/GHSA-rfx7-4xw3-gh4m) + was a plain path traversal in the entry name. The containment check built an Error + object without throwing it, so an entry literally named something like + was written outside the destination. That issue was fixed in @appium/support 7.0.6 + by actually rejecting out of bound entry n

    gitlab.com
  • NIST NVDVulnerability recordCVE-2026-103975

    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

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-qfxx-c367-67f8

    Appium: Symlink based Zip Slip in @appium/support ZIP extraction

    osv.dev

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.