cve.bz

CVE-2026-103975 appium appium: Link Following

6.5 mediumEPSS 0.6%Fix available

Medium (6.5) in appium appium. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in @appium/support 7.2.6.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @appium/support (npm): fixed in 7.2.6

Ask an AI about this CVE

Show the promptExplain CVE-2026-103975 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103975?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103975?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103975 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
appium< 7.2.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qfxx-c367-67f8npm@appium/support<7.2.67.2.6

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity vulnerability was found in the ZIP extraction utility of the @appium/support npm package of Appium, an automation framework built on the W3C WebDriver protocol; no Red Hat products are currently recorded as affected by this flaw. The extractor applies only a lexical containment check to archive entry names and does not validate symbolic link targets. A crafted ZIP archive can first create a symbolic link pointing to a directory outside the extraction directory and then include a regular-file entry whose legitimate name resolves through that link, causing the file to be written outside the extraction root. When a user or automated pipeline extracts an attacker-supplied archive, this allows an attacker to create or overwrite files at any location writable by the Appium process, which can lead to arbitrary code execution if configuration files, startup scripts, or executables are overwritten. This vector is distinct from a previously fixed entry-name path traversal in the same code because it uses no parent-directory or absolute entry names, so name-based defenses accept every entry. The Red Hat and upstream severity assessments match (moderate, CVSS 3.1 score of 6.5).

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103975.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON