What is CVE-2026-43910?

CVE-2026-43910 is a high-severity server-side request forgery (SSRF) vulnerability in io.appium:java-client (maven), affecting versions >= 8.2.1, <= 10.1.0. It is fixed in 10.1.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2026-43910?

CVE-2026-43910 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of io.appium:java-client are affected by CVE-2026-43910?

io.appium:java-client (maven) versions >= 8.2.1, <= 10.1.0 is affected.

Is there a fix for CVE-2026-43910?

Yes. CVE-2026-43910 is fixed in 10.1.1. Upgrade to this version or later.

Is CVE-2026-43910 exploitable, and should I be worried?

Whether CVE-2026-43910 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-43910 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-43910?

Upgrade io.appium:java-client to 10.1.1 or later.

CVE-2026-43910 in io.appium:java-client

Q: How severe is CVE-2026-43910?

CVE-2026-43910 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of io.appium:java-client are affected by CVE-2026-43910?

io.appium:java-client (maven) versions >= 8.2.1, <= 10.1.0 is affected.

Q: Is there a fix for CVE-2026-43910?

Yes. CVE-2026-43910 is fixed in 10.1.1. Upgrade to this version or later.

Q: Is CVE-2026-43910 exploitable, and should I be worried?

Whether CVE-2026-43910 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-43910 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-43910?

Upgrade io.appium:java-client to 10.1.1 or later.

Summary

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

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:

Screenshot 2, Java client processing response from attacker host:

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

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-43910 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (10.1.1); upgrading removes the vulnerable code path.

Affected versions

io.appium:java-client (>= 8.2.1, <= 10.1.0)

Security releases

io.appium:java-client → 10.1.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Add allowlist validation before overrideServerUrl() is called, and/or
block RFC-1918/loopback/link-local destinations by default.

poc_appium_directconnect.zip

Frequently Asked Questions

What is CVE-2026-43910? CVE-2026-43910 is a high-severity server-side request forgery (SSRF) vulnerability in io.appium:java-client (maven), affecting versions >= 8.2.1, <= 10.1.0. It is fixed in 10.1.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
How severe is CVE-2026-43910? CVE-2026-43910 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of io.appium:java-client are affected by CVE-2026-43910? io.appium:java-client (maven) versions >= 8.2.1, <= 10.1.0 is affected.
Is there a fix for CVE-2026-43910? Yes. CVE-2026-43910 is fixed in 10.1.1. Upgrade to this version or later.
Is CVE-2026-43910 exploitable, and should I be worried? Whether CVE-2026-43910 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-43910 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-43910? Upgrade io.appium:java-client to 10.1.1 or later.