Vulnerability in @appium/support (CVE-2026-103975)
Summary
Vulnerability in @appium/support (CVE-2026-103975). Data can be tampered with by attackers. Exploitable via pwn. Mitigation: upgrade to 7.0.6 or later.
Original description
The description as published by the source.
Summary
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 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.
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 |
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-103975 has been found in @appium/support.
Attackers can target a specific entry point like pwn over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @appium/support to 7.0.6 or later.
If unsure, ask your IT team or search "@appium/support CVE-2026-103975" on the vendor's site.
CVE-2026-103975 (@appium/support) — CWE-59 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: pwn / isSubPath / dir
Patched: 7.0.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in @appium/support. Attackers reach the vulnerable code path via pwn without authentication.
Check the vendor advisory for the affected versions of @appium/support. Attack surface: pwn / isSubPath / dir.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 7.0.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@appium/support' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@appium/support' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@appium/supportを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @appium/support to 7.0.6ステージング環境で 7.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。