Vulnerability in io.appium:java-client (CVE-2026-43910)
Summary
Vulnerability in io.appium:java-client (CVE-2026-43910). Confidential information can be exposed externally. Exploitable via POST /wd/hub/session. Mitigation: upgrade to 10.1.1 or later.
Original description
The description as published by the source.
Appium Java Client is the Java language binding for writing Appium tests that conform to the W3C WebDriver protocol. From 8.2.1 until 10.1.1, when directConnect(true) is enabled, AppiumCommandExecutor.setDirectConnect() reads the directConnectHost, directConnectPort, and directConnectPath fields from the server's NEW_SESSION response and rebuilds the client's server URL from them, validating only that the protocol is https, with no host allowlist or IP validation; a rogue or compromised server can therefore redirect all subsequent session traffic to an arbitrary destination, enabling full interception of session traffic and a server-side request forgery pivot to internal hosts, including cloud metadata (IMDS) credential theft. This vulnerability is fixed in 10.1.1.
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-43910 has been found in io.appium:java-client.
Attackers can target a specific entry point like POST /wd/hub/session over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade io.appium:java-client to 10.1.1 or later.
If unsure, ask your IT team or search "io.appium:java-client CVE-2026-43910" on the vendor's site.
CVE-2026-43910 (io.appium:java-client) — CWE-441 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /wd/hub/session / GET /wd/hub/session/poc-session-001/source / DELETE /wd/hub/session/poc-session-001 / directConnectHost
Patched: 10.1.1 — 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-441) exists in io.appium:java-client. Attackers reach the vulnerable code path via POST /wd/hub/session without authentication.
Check the vendor advisory for the affected versions of io.appium:java-client. Attack surface: POST /wd/hub/session / GET /wd/hub/session/poc-session-001/source / DELETE /wd/hub/session/poc-session-001 / directConnectHost.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 10.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /wd/hub/session requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.appium:java-client を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /wd/hub/session' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /wd/hub/sessionへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade io.appium:java-client to 10.1.1ステージング環境で 10.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /wd/hub/session on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com