`CVE-2026-43910`

8.2 High No exploit published

Published 49 days ago. NVD backfills CPE data for days or weeks after publication, and OSV and the exploit indexes lag too. Scope and status here may change.

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.

CWE-441CWE-918 · Server-side request forgery

Exploitation Status

Proof of concept only

A proof of concept exists, but no reviewed exploit catalogue carries this CVE. Demonstrating a defect and weaponising it are different amounts of work.

CVSS E:P

CISA KEV not listed
CISA Vulnrichment exploitation: poc CISA concluded an exploit has been demonstrated, typically from a vendor advisory, which leaves no artifact to index. Automatable: no, technical impact: partial.
Indexed PoC none indexed
EPSS 0.30% chance in 30 days

Waratek Defense Posture

No exploit published

In RASP's scope with an upstream fix path, but nobody has published a working exploit. That is a statement about what has been published, not a finding that the defect is unreachable or unimportant.

Protection none
Action unverified patch rule
Review automated upstream-data
Record active

Decided by no-exploit-published : A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all

Finding This CVE is not listed in CISA KEV, CISA Vulnrichment records no active exploitation, and no reviewed exploit catalogue carries an entry for it. Nobody has published something a stranger can run, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Candidate fix https://github.com/appium/java-client/commit/2b9cd442b9dbf56ccc6f1e83aeeb411c0ec230c9 : a commit: the change itself

Decided by	`no-exploit-published` : A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all
Finding	This CVE is not listed in CISA KEV, CISA Vulnrichment records no active exploitation, and no reviewed exploit catalogue carries an entry for it. Nobody has published something a stranger can run, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix	https://github.com/appium/java-client/commit/2b9cd442b9dbf56ccc6f1e83aeeb411c0ec230c9 : a commit: the change itself

CVSS

8.2 HIGH v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N 1 metric

VRT selects the newest version's highest entry and publishes it as cvssScore, newest rather than largest because scores are not comparable across versions, and highest rather than first because the first entry is frequently a CNA placeholder scoring 0.0 over NVD's own analysis.

Version Score Band Vector Assigner Type

CVSS 3.1 8.2 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N security-advisories@github.com Secondary published

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	8.2	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`	security-advisories@github.com	Secondary	published

Affected Software & Releases

☕ Maven Library Packages

Artifact coordinates and fix boundaries from OSV.dev

Package Coordinate Introduced Fixed Last affected

io.appium:java-client 8.2.1 10.1.1 unbounded

Package Coordinate	Introduced	Fixed	Last affected
`io.appium:java-client`	8.2.1	`10.1.1`	unbounded

🖥️ Product CPEs & Version Ranges

2 product(s) over 2 version claims (uncapped)

Source	Vendor	Product	Scheme	Affected Versions
nvd	appium	java-client	generic	≥ 8.2.1 and ＜ 10.1.1
osv	io.appium	java-client	generic	≥ 8.2.1 and ＜ 10.1.1

Source

Vendor

Product

Scheme

Affected Versions

nvd

appium

java-client

generic

≥ 8.2.1 and ＜ 10.1.1

osv

io.appium

java-client

generic

≥ 8.2.1 and ＜ 10.1.1

References

URL	Tags
https://github.com/appium/java-client/commit/2b9cd442b9dbf56ccc6f1e83aeeb411c0ec230c9	commit
https://github.com/appium/java-client/security/advisories/GHSA-28f5-38xr-jh2w	WEB
https://github.com/appium/java-client/pull/2408	WEB
https://github.com/appium/java-client	PACKAGE
https://github.com/appium/java-client/releases/tag/v10.1.1	WEB

URL

Timeline

Published 2026-07-28 Last modified 2026-08-07

Published	2026-07-28	By the CVE Program.
NVD record modified	2026-08-07	NVD's own last-modified date for this record.

Published

2026-07-28

By the CVE Program.

NVD record modified

2026-08-07

NVD's own last-modified date for this record.

Pipeline policy audit (15 of 21 rules evaluated)

15 of 21 rules ran. The rest were never reached, because an earlier stage settled the CVE, a distinct claim from a rule that ran and found nothing.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? first match wins

1 rejected no-match CVE Program withdrawal of this identifier

scope: Is the vulnerability ARMR's to address? first match wins

2 armr-patch-file no-match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no-match An ARMR security-rule template on disk for this CVE

4 manual-classification no-match A researcher's recorded decision for this specific CVE

5 manual classification no-match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no-match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no-match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the native WebLogic proxy plug-in. Oracle gives these no CPE of their own and names them only in the description.

8 osv-maven matched Queued for review Maven packages: io.appium:java-client

9 cna-maven-package not-reached An affected Maven artifact named by the CNA itself

10 known-cpe-product not-reached An NVD CPE naming a product ARMR tracks

11 cna-cpe-product not-reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

12 oracle-advisory-family not-reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

13 non-deployable-product not-reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

14 unmatched-product not-reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? cumulative: every rule gets a turn

15 patch-hint matched Mitigation candidate References include candidate fix URL (commit tier): https://github.com/appium/java-client/commit/2b9cd442b9dbf56ccc6f1e83aeeb411c0ec230c9

16 open-source-maven skipped The affected package being open source on Maven, so the fix can be read

17 poc-derivable skipped An indexed exploit to reverse-engineer, where there is no source to read

18 no-exploit skipped With no fix path, a public exploit, or a CISA record of one

19 secure-rule-match no-match A vulnerability class already blocked by an ARMR security rule

20 below-action-threshold no-match Severity is HIGH — only MEDIUM/LOW are deprioritized

21 no-exploit-published decided it matched No exploit published No working exploit has been published, and an upstream fix path does exist, so the remediation half of the candidacy still holds.

What the scope rules read

The products the record named, and whether known-products.yaml tracks them. This is the evidence the scope stage decided on.

Vendor Product Tracked CPE Source

appium java-client not tracked cpe:2.3:a:appium:java-client:*:*:*:*:*:*:*:*

Raw stored JSON document for this CVE ↗ · NVD ↗ · CVE.org ↗