Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor

CVE-2026-43910GHSA-28f5-38xr-jh2w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (io.appium:java-client 10.1.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-43910: 0.43% estimated exploitation activity in the next 30 days; percentile 37.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary When directConnect(true) is enabled, appium/java-client unconditionally accepts directConnectHost, directConnectPort, and directConnectPath from the server's NEWSESSION 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 -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-28f5-38xr-jh2w

  2. Revision 1 · created ·

    Published from osv record GHSA-28f5-38xr-jh2w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-43910

Advisory: java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor
IDs: CVE-2026-43910, GHSA-28f5-38xr-jh2w
Record: https://patchnext.com/advisories/cve-2026-43910 (revision 2, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.appium:java-client 10.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.appium:java-client: affected >= 8.2.1, <= 10.1.0; fixed in 10.1.1

## Suggested inspection (read-only)
- Maven io.appium:java-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.appium:java-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-28f5-38xr-jh2w (OSV record GHSA-28f5-38xr-jh2w lists affected ranges: Maven io.appium:java-client >=8.2.1 <10.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-28f5-38xr-jh2w (GitHub-reviewed advisory GHSA-28f5-38xr-jh2w lists affected ranges: Maven io.appium:java-client >=8.2.1 <=10.1.0)

Commands are suggestions: review each one before running it.

Loading voting…