Vulnerability Database · Maven · Package report

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

io.kubernetes:client-java is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 29 releases, from Jan 2021 to Oct 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on io.kubernetes:client-java 27.0.1 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 27.0.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 12 Oct 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 11 packages i
  • Stars 4,001 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.kubernetes:client-java, 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
27.0.1 14 Oct 2026 none Apache-2.0 — Details →
27.0.0 01 Jul 2026 none Apache-2.0 — Details →
25.0.1 23 Jun 2026 none Apache-2.0 — Details →
26.0.1 10 Jun 2026 none Apache-2.0 — Details →
26.0.0 30 Mar 2026 none Apache-2.0 — Details →
25.0.0-legacy 25 Nov 2025 none Apache-2.0 — Details →
25.0.0 25 Nov 2025 none Apache-2.0 — Details →
19.0.3 05 Jun 2025 none Apache-2.0 — Details →
24.0.0-legacy 23 May 2025 none Apache-2.0 — Details →
24.0.0 23 May 2025 none Apache-2.0 — Details →
23.0.0-legacy 19 Feb 2025 none Apache-2.0 — Details →
23.0.0 19 Feb 2025 none Apache-2.0 — Details →
22.0.1-legacy 11 Feb 2025 none Apache-2.0 — Details →
22.0.1 11 Feb 2025 none Apache-2.0 — Details →
22.0.0-legacy 22 Jan 2025 none Apache-2.0 — Details →
21.0.2-legacy 18 Jan 2025 none Apache-2.0 — Details →
19.0.2 08 Dec 2024 none Apache-2.0 — Details →
22.0.0 08 Nov 2024 none Apache-2.0 — Details →
21.0.2 09 Oct 2024 none Apache-2.0 — Details →
21.0.1-legacy 24 Aug 2024 none Apache-2.0 — Details →
21.0.1 30 Jul 2024 none Apache-2.0 — Details →
21.0.0-legacy 21 Jun 2024 none Apache-2.0 — Details →
21.0.0 21 Jun 2024 none Apache-2.0 — Details →
20.0.1-legacy 23 Mar 2024 none Apache-2.0 — Details →
19.0.1 14 Mar 2024 none Apache-2.0 — Details →
20.0.1 13 Mar 2024 none Apache-2.0 — Details →
20.0.0-legacy 10 Feb 2024 none Apache-2.0 — Details →
20.0.0 07 Feb 2024 none Apache-2.0 — Details →
19.0.0 18 Oct 2023 none Apache-2.0 — Details →
18.0.1 10 Jul 2023 none Apache-2.0 — Details →
17.0.2 14 Apr 2023 none Apache-2.0 — Details →
18.0.0 03 Mar 2023 none Apache-2.0 — Details →
17.0.1 31 Jan 2023 none Apache-2.0 — Details →
16.0.3 30 Jan 2023 none Apache-2.0 — Details →
15.0.2 30 Jan 2023 none Apache-2.0 — Details →
17.0.0 08 Dec 2022 none Apache-2.0 — Details →
16.0.2 03 Nov 2022 none Apache-2.0 — Details →
16.0.1 20 Oct 2022 none Apache-2.0 — Details →
16.0.0 28 Jun 2022 none Apache-2.0 — Details →
15.0.1 19 Apr 2022 none Apache-2.0 — Details →
15.0.0 28 Mar 2022 none Apache-2.0 — Details →
14.0.1 05 Mar 2022 none Apache-2.0 — Details →
13.0.2 11 Jan 2022 none Apache-2.0 — Details →
11.0.4 07 Jan 2022 none Apache-2.0 — Details →
10.0.2 31 Dec 2021 M1 Apache-2.0 Yes Details →
14.0.0 12 Nov 2021 none Apache-2.0 — Details →
12.0.2 01 Nov 2021 none Apache-2.0 — Details →
11.0.3 31 Oct 2021 none Apache-2.0 — Details →
13.0.1 15 Oct 2021 none Apache-2.0 — Details →
13.0.0 15 Jul 2021 none Apache-2.0 — Details →
12.0.1 13 May 2021 none Apache-2.0 — Details →
11.0.2 13 May 2021 none Apache-2.0 — Details →
12.0.0 13 Mar 2021 none Apache-2.0 — Details →
11.0.1 03 Mar 2021 none Apache-2.0 — Details →
11.0.0 21 Dec 2020 M1 Apache-2.0 Yes Details →
10.0.1 21 Dec 2020 M1 Apache-2.0 Yes Details →
9.0.3 18 Dec 2020 M1 Apache-2.0 Yes Details →
10.0.0 17 Sep 2020 M1 Apache-2.0 Yes Details →
9.0.2 18 Aug 2020 M1 Apache-2.0 Yes Details →
9.0.1 12 Aug 2020 H1 M1 Apache-2.0 Yes Details →
9.0.0 23 Jul 2020 H1 M1 Apache-2.0 Yes Details →
8.0.2 19 May 2020 H1 M1 Apache-2.0 Yes Details →
8.0.0 10 Mar 2020 H1 M1 Apache-2.0 Yes Details →
8.0.0-alpha1 18 Feb 2020 H1 M1 Apache-2.0 Yes Details →
7.0.0 06 Dec 2019 H1 M1 Apache-2.0 Yes Details →
6.0.1 27 Aug 2019 H1 M1 Apache-2.0 Yes Details →
5.0.0 31 May 2019 H1 M1 Apache-2.0 Yes Details →
4.0.0 11 Feb 2019 H1 M1 Apache-2.0 Yes Details →
4.0.0-beta1 05 Nov 2018 H1 M1 Apache-2.0 Yes Details →
3.0.0 25 Oct 2018 H1 M1 Apache-2.0 Yes Details →
3.0.0-beta2 08 Sep 2018 H1 M1 Apache-2.0 Yes Details →
3.0.0-beta1 27 Jul 2018 H1 M1 Apache-2.0 Yes Details →
2.0.0 14 Jul 2018 H1 M1 Apache-2.0 Yes Details →
2.0.0-beta2 13 Jul 2018 H1 M1 Apache-2.0 Yes Details →
2.0.0-beta1 22 May 2018 H1 M1 Apache-2.0 Yes Details →
1.0.0 20 Apr 2018 H1 M1 Apache-2.0 Yes Details →
1.0.0-beta4 04 Apr 2018 H1 M1 Apache-2.0 Yes Details →
1.0.0-beta3 24 Mar 2018 H1 M1 Apache-2.0 Yes Details →
1.0.0-beta2 19 Jan 2018 H1 M1 Apache-2.0 Yes Details →
1.0.0-beta1 04 Oct 2017 H1 M1 Apache-2.0 Yes Details →
0.2 25 Sep 2017 H1 M1 Apache-2.0 Yes Details →
0.1 11 Aug 2017 H1 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for io.kubernetes:client-java

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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.kubernetes:client-java

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

Vulert records 2 vulnerabilities for io.kubernetes:client-java in Maven: 0 critical, 1 high, 1 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.kubernetes:client-java's Vulert package health score?

Vulert scores io.kubernetes:client-java 82/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.kubernetes:client-java affected?

No. 27.0.1, 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.

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

2 vulnerabilities are recorded for io.kubernetes:client-java in the Maven ecosystem: 0 critical, 1 high, 1 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.kubernetes:client-java vulnerabilities disclosed?

0 vulnerabilities were recorded for io.kubernetes:client-java in the last 12 months, and the oldest entry in this database dates to 29 Jan 2021. 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.kubernetes:client-java 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.kubernetes:client-java for upcoming vulnerabilities?

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