Answer in brief
CVE-2026-43910 records a High severity secret exfiltration vulnerability in java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-43910 records a High severity secret exfiltration vulnerability in java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update io.appium:java-client to 10.1.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSecret Exfiltration describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-43910 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| io.appium:java-clientmaven | >=8.2.1,<=10.1.0 | 10.1.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-43910 records a High severity secret exfiltration vulnerability in java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for io.appium:java-client.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate io.appium:java-client to 10.1.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSecret Exfiltration describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-43910 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| io.appium:java-clientmaven | >=8.2.1,<=10.1.0 | 10.1.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-43910 records a High severity secret exfiltration vulnerability in java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for io.appium:java-client.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard## Summary When `directConnect(true)` is enabled, appium/java-client unconditionally accepts `directConnectHost`, `directConnectPort`, and `directConnectPath` from the server's NEW_SESSION response and silently redirects all subsequent session traffic to the attacker-specified endpoint — with no allowlist, no host validation, and no user notification. ## Affected Code - `AppiumCommandExecutor.java` (line 196–219): `setDirectConnect()` builds a new URL from server-supplied fields and calls `overrideServerUrl(newUrl)` without validating host/IP. - `DirectConnect.java`: `getUrl()` constructs `protocol://host:port/path` with no allowlist. ## Root Cause Only the protocol is validated (must equal "https"). The destination host and port are never checked against any allowlist or denylist. ## PoC (confirmed) A rogue server injecting `directConnectHost=127.0.0.1:4443` causes the client to silently redirect all post-session commands: [bootstrap] POST /wd/hub/session [bootstrap] Injecting directConnect -> https://127.0.0.1:4443/wd/hub [redirect-target] HIT #1: GET /wd/hub/session/poc-session-001/source [redirect-target] HIT #2: DELETE /wd/hub/session/poc-session-001 Original source code unmodified — confirmed via `git diff HEAD` (empty). ## Evidence Screenshots **Screenshot 1 — Rogue server capturing redirected traffic:** <img width="887" height="146" alt="1" src="https://github.com/user-attachments/assets/cc28002c-ea20-4ac8-8336-cec632e3c842" /> **Screenshot 2 — Java client processing response from attacker host:** <img width="788" height="130" alt="2" src="https://github.com/user-attachments/assets/222cbab0-0d53-45b2-847d-6aa4e3b79370" /> ## Impact - Full interception of session traffic - Network pivot to internal hosts (RFC-1918, 169.254.169.254) - Cloud credential theft via IMDS endpoint - Escalates to ~8.1 High in CI/CD environments where directConnect(true) is set in shared base configuration ## Suggested Fix Add allowlist validation before `overrideServerUrl()` is called, and/or block RFC-1918/loopback/link-local destinations by default. [poc_appium_directconnect.zip](https://github.com/user-attachments/files/26472525/poc_appium_directconnect.zip)
## Summary When `directConnect(true)` is enabled, appium/java-client unconditionally accepts `directConnectHost`, `directConnectPort`, and `directConnectPath` from the server's NEW_SESSION response and silently redirects all subsequent session traffic to the attacker-specified endpoint — with no allowlist, no host validation, and no user notification. ## Affected Code - `AppiumCommandExecutor.java` (line 196–219): `setDirectConnect()` builds a new URL from server-supplied fields and calls `overrideServerUrl(newUrl)` without validating host/IP. - `DirectConnect.java`: `getUrl()` constructs `protocol://host:port/path` with no allowlist. ## Root Cause Only the protocol is validated (must equal "https"). The destination host and port are never checked against any allowlist or denylist. ## PoC (confirmed) A rogue server injecting `directConnectHost=127.0.0.1:4443` causes the client to silently redirect all post-session commands: [bootstrap] POST /wd/hub/session [bootstrap] Injecting directConnect -> https://127.0.0.1:4443/wd/hub [redirect-target] HIT #1: GET /wd/hub/session/poc-session-001/source [redirect-target] HIT #2: DELETE /wd/hub/session/poc-session-001 Original source code unmodified — confirmed via `git diff HEAD` (empty). ## Evidence Screenshots **Screenshot 1 — Rogue server capturing redirected traffic:** <img width="887" height="146" alt="1" src="https://github.com/user-attachments/assets/cc28002c-ea20-4ac8-8336-cec632e3c842" /> **Screenshot 2 — Java client processing response from attacker host:** <img width="788" height="130" alt="2" src="https://github.com/user-attachments/assets/222cbab0-0d53-45b2-847d-6aa4e3b79370" /> ## Impact - Full interception of session traffic - Network pivot to internal hosts (RFC-1918, 169.254.169.254) - Cloud credential theft via IMDS endpoint - Escalates to ~8.1 High in CI/CD environments where directConnect(true) is set in shared base configuration ## Suggested Fix Add allowlist validation before `overrideServerUrl()` is called, and/or block RFC-1918/loopback/link-local destinations by default. [poc_appium_directconnect.zip](https://github.com/user-attachments/files/26472525/poc_appium_directconnect.zip)