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

Advisory record · `GHSA-28f5-38xr-jh2w`

- **Identifiers:** `GHSA-28f5-38xr-jh2w` · `CVE-2026-43910`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-441](https://cwe.mitre.org/data/definitions/441.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md) · [CWE-441](https://agentprime.io/advisories/tag/cwe-441.md)
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Jul 2026, 14:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.appium:java-client` (Maven): affected `>=8.2.1, <10.1.1`; fixed in `10.1.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected: io.appium:java-client versions 8.2.1 up to but not including 10.1.1. When directConnect(true) is enabled, the client accepts the host, port and path for a redirect from the Appium server's new-session response and sends all later session traffic there without checking the destination. An attacker who can make the Appium server return such a response can intercept session traffic and reach internal hosts. Upgrade to 10.1.1 or later.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-28f5-38xr-jh2w)

## Sources

- [GitHub Advisory Database: GHSA-28f5-38xr-jh2w](https://github.com/advisories/GHSA-28f5-38xr-jh2w)
- [OSV: GHSA-28f5-38xr-jh2w](https://osv.dev/vulnerability/GHSA-28f5-38xr-jh2w)
- <https://github.com/appium/java-client/security/advisories/GHSA-28f5-38xr-jh2w>
- <https://github.com/appium/java-client/pull/2408>
- <https://github.com/appium/java-client/commit/2b9cd442b9dbf56ccc6f1e83aeeb411c0ec230c9>
- <https://github.com/appium/java-client>
- <https://github.com/appium/java-client/releases/tag/v10.1.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-28f5-38xr-jh2w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-28f5-38xr-jh2w/>. Everything for agents: <https://agentprime.io/llms.txt>.