{"answers":{"affected":"2 open source packages ship an affected version, including @appium/support.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103975 exists.","fix":"Upgrade @appium/support to 7.2.6 or later.","what":"CVE-2026-103975 is a medium-severity path traversal vulnerability in appium, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-103975 and fix it if it is affected.\n\nWhat it is: CVE-2026-103975 is a medium-severity path traversal vulnerability in appium, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-103975 exists.\n\nAffected packages and fixed versions:\n- @appium/support (npm): affected all versions; fixed in 7.2.6\n- @appium/support (npm): affected all versions; fixed in 7.2.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-103975/ (Markdown: https://insights.sbomify.com/CVE-2026-103975/index.md)","id":"CVE-2026-103975","markdown":"https://insights.sbomify.com/CVE-2026-103975/index.md","name":"CVE-2026-103975","record":{"aliases":["GHSA-qfxx-c367-67f8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Appium support library","requires_auth":"none","summary":"Attackers can exploit symlink-based Zip Slip in Appium's ZIP extraction to write arbitrary files, potentially leading to code execution.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Appium: Symlink based Zip Slip in @appium/support ZIP extraction","id":"CVE-2026-103975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"FileRise: Session-scoped TOTP rate limiting permits repeated verification attempts","id":"CVE-2026-103977"},"packages":[{"ecosystem":"npm","fixed":["7.2.6"],"introduced":["0"],"last_affected":[],"package":"@appium/support","purl":null,"source":"GHSA-qfxx-c367-67f8"},{"ecosystem":"npm","fixed":["7.2.6"],"introduced":["0"],"last_affected":[],"package":"@appium/support","purl":"pkg:npm/%40appium/support","source":"GHSA-qfxx-c367-67f8"}],"prev":{"headline":"lichess.org: Stored HTML Injection via PGN Annotator Tag in Studies","id":"CVE-2026-103974"},"products":["appium"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["appium"]},"summary":"Attackers can exploit symlink-based Zip Slip in Appium's ZIP extraction to write arbitrary files, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-103975/"}