CVE-2026-43910: appium java-client · Confused Deputy
Affects appium java-clientSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 10.1.1 soon.
Data as of 27 Oct 2026, 05:11 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.1.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade appium java-client to 10.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| appiumjava-client | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in Appium Java Client version 10.1.1. Users should upgrade to version 10.1.1 or later to remediate this issue. Until upgrading, users should consider disabling directConnect(true) to avoid triggering the vulnerable code path. Patch status is not explicitly confirmed beyond the fix in 10.1.1; users should consult the official Appium project advisories for the latest remediation guidance.
Description
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.
References
- github.com/appium/java-client/security/advisories/GHSA-28f5-38xr-jh2w (opens in a new tab)
- github.com/appium/java-client/pull/2408 (opens in a new tab)
- github.com/appium/java-client/commit/2b9cd442b9dbf56ccc6f1e83aeeb411c0ec230c9 (opens in a new tab)
- github.com/appium/java-client/releases/tag/v10.1.1 (opens in a new tab)