Vulnerability Database · Maven · Package report

io.appium:java-client: vulnerability history, versions and safety

io.appium:java-client is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 17 releases, first recorded in Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 28 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on io.appium:java-client 11.0.0 i

Updated on 23 Oct 2026

Good news: 11.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 11.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 11.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 11.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 28 Jul 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 19 packages i
  • Stars 1,283 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for io.appium:java-client, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
11.0.0 07 Oct 2026 none Apache-2.0 — Details →
10.1.1 20 Apr 2026 none Apache-2.0 — Details →
10.1.0 11 Mar 2026 H1 Apache-2.0 Yes Details →
10.0.0 13 Aug 2025 H1 Apache-2.0 Yes Details →
9.5.0 01 Jul 2025 H1 Apache-2.0 Yes Details →
9.4.0 21 Jan 2025 H1 Apache-2.0 Yes Details →
9.3.0 28 Jul 2024 H1 Apache-2.0 Yes Details →
9.2.3 28 May 2024 H1 Apache-2.0 Yes Details →
9.2.2 28 Mar 2024 H1 Apache-2.0 Yes Details →
9.2.1 28 Mar 2024 H1 Apache-2.0 Yes Details →
9.2.0 14 Mar 2024 H1 Apache-2.0 Yes Details →
9.1.0 27 Jan 2024 H1 Apache-2.0 Yes Details →
9.0.0 14 Oct 2023 H1 Apache-2.0 Yes Details →
8.6.0 09 Oct 2023 H1 Apache-2.0 Yes Details →
8.5.1 02 Jun 2023 H1 Apache-2.0 Yes Details →
8.5.0 09 May 2023 H1 Apache-2.0 Yes Details →
8.4.0 07 May 2023 H1 Apache-2.0 Yes Details →
8.3.0 02 Dec 2022 H1 Apache-2.0 Yes Details →
8.2.1 25 Nov 2022 H1 Apache-2.0 Yes Details →
8.2.0 30 Aug 2022 none Apache-2.0 — Details →
8.1.1 05 Jun 2022 none Apache-2.0 — Details →
8.1.0 30 May 2022 none Apache-2.0 — Details →
8.0.0 07 Mar 2022 none Apache-2.0 — Details →
8.0.0-beta2 22 Dec 2021 none Apache-2.0 — Details →
8.0.0-beta 02 Nov 2021 none Apache-2.0 — Details →
7.6.0 11 Oct 2021 none Apache-2.0 — Details →
7.5.1 25 Mar 2021 none Apache-2.0 — Details →
7.5.0 13 Mar 2021 none Apache-2.0 — Details →
7.4.1 30 Nov 2020 none Apache-2.0 — Details →
7.4.0 17 Nov 2020 none Apache-2.0 — Details →
7.3.0 11 Nov 2019 none Apache-2.0 — Details →
7.2.0 19 Aug 2019 none Apache-2.0 — Details →
7.1.0 06 Jul 2019 none Apache-2.0 — Details →
7.0.0 27 Dec 2018 none Apache-2.0 — Details →
6.1.0 21 Jun 2018 none Apache-2.0 — Details →
6.0.0 24 May 2018 none Apache-2.0 — Details →
6.0.0-BETA5 18 Apr 2018 none Apache-2.0 — Details →
6.0.0-BETA4 07 Mar 2018 none Apache-2.0 — Details →
6.0.0-BETA3 15 Feb 2018 none Apache-2.0 — Details →
6.0.0-BETA2 23 Dec 2017 none Apache-2.0 — Details →
6.0.0-BETA1 03 Dec 2017 none Apache-2.0 — Details →
5.0.4 02 Oct 2017 none Apache-2.0 — Details →
5.0.3 10 Sep 2017 none Apache-2.0 — Details →
5.0.2 03 Sep 2017 none Apache-2.0 — Details →
5.0.1 28 Aug 2017 none Apache-2.0 — Details →
5.0.0 26 Aug 2017 none Apache-2.0 — Details →
5.0.0-BETA9 16 Jun 2017 none Apache-2.0 — Details →
5.0.0-BETA8 26 Apr 2017 none Apache-2.0 — Details →
5.0.0-BETA7 11 Apr 2017 none Apache-2.0 — Details →
5.0.0-BETA6 22 Mar 2017 none Apache-2.0 — Details →
5.0.0-BETA5 06 Mar 2017 none Apache-2.0 — Details →
5.0.0-BETA4 28 Feb 2017 none Apache-2.0 — Details →
5.0.0-BETA3 13 Feb 2017 none Apache-2.0 — Details →
5.0.0-BETA2 04 Feb 2017 none Apache-2.0 — Details →
5.0.0-BETA1 28 Dec 2016 none Apache-2.0 — Details →
4.1.2 21 Aug 2016 none Apache-2.0 — Details →
4.1.1 06 Aug 2016 none Apache-2.0 — Details →
4.1.0 02 Aug 2016 none Apache-2.0 — Details →
4.0.0 29 May 2016 none Apache-2.0 — Details →
3.4.1 30 Mar 2016 none Apache-2.0 — Details →
3.4.0 06 Mar 2016 none Apache-2.0 — Details →
3.3.0 10 Dec 2015 none Apache-2.0 — Details →
3.2.0 15 Sep 2015 none Apache-2.0 — Details →
3.1.0 06 Jul 2015 none Apache-2.0 — Details →
3.0.0 19 Jun 2015 none Apache-2.0 — Details →
2.2.0 13 Mar 2015 none Apache-2.0 — Details →
2.1.0 14 Nov 2014 none Apache-2.0 — Details →
2.0.0 29 Sep 2014 none Apache-2.0 — Details →
1.7.0 10 Sep 2014 none Apache-2.0 — Details →
1.6.2 14 Aug 2014 none Apache-2.0 — Details →
1.6.1 05 Aug 2014 none Apache-2.0 — Details →
1.6.0 29 Jul 2014 none Apache-2.0 — Details →
1.5.0 11 Jul 2014 none Apache-2.0 — Details →
1.4.0 16 Jun 2014 none Apache-2.0 — Details →
1.3.0 02 Jun 2014 none Apache-2.0 — Details →
1.2.1 21 May 2014 none Apache-2.0 — Details →
1.2.0 19 May 2014 none Apache-2.0 — Details →
1.1.0 06 May 2014 none Apache-2.0 — Details →
1.0.2 02 May 2014 none Apache-2.0 — Details →
1.0.1 02 May 2014 none Apache-2.0 — Details →
1.0 22 Apr 2014 none Apache-2.0 — Details →

All 81 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for io.appium:java-client

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About io.appium:java-client

Is io.appium:java-client safe to use?

Vulert records 1 vulnerabilities for io.appium:java-client in Maven: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is io.appium:java-client's Vulert package health score?

Vulert scores io.appium:java-client 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of io.appium:java-client affected?

No. 11.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of io.appium:java-client should I use?

11.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does io.appium:java-client have?

1 vulnerability is recorded for io.appium:java-client in the Maven ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.appium:java-client vulnerabilities disclosed?

1 vulnerability was recorded for io.appium:java-client in the last 12 months, and the oldest entry in this database dates to 28 Jul 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of io.appium:java-client are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor io.appium:java-client for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the io.appium:java-client version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.