VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.eclipse.milo:sdk-client: vulnerability history, versions and safety

org.eclipse.milo:sdk-client is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 25 releases, first recorded in Mar 2020. 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
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.

See all org.eclipse.milo:sdk-client vulnerabilities

Vulert verdict on org.eclipse.milo:sdk-client 0.6.16 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

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

  • Current release 0.6.16 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 16 Mar 2020 i
  • Highest CVSS 7.4 i
  • With no published fix 0 i
  • Depended on by 9 packages i
  • Stars 1,393 i
  • OpenSSF scorecard 5/10 i
  • Last release 18 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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 org.eclipse.milo:sdk-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
0.6.16 21 Apr 2025 none non-standard — Details →
0.6.15 03 Dec 2024 none non-standard — Details →
0.6.14 01 Aug 2024 none non-standard — Details →
0.6.13 18 May 2024 none non-standard — Details →
0.6.12 31 Jan 2024 none non-standard — Details →
0.6.11 06 Sep 2023 none non-standard — Details →
0.6.10 20 Jun 2023 none non-standard — Details →
0.6.9 03 Apr 2023 none non-standard — Details →
0.6.8 02 Sep 2022 none non-standard — Details →
0.6.7 28 Jun 2022 none non-standard — Details →
0.6.6 19 May 2022 none non-standard — Details →
0.6.5 15 Apr 2022 none non-standard — Details →
0.6.4 24 Feb 2022 none non-standard — Details →
0.6.3 28 Jun 2021 none non-standard — Details →
0.6.2 28 Jun 2021 none non-standard — Details →
0.6.1 22 Apr 2021 none non-standard — Details →
0.6.1-M1 22 Apr 2021 none non-standard — Details →
0.6.0 26 Mar 2021 none non-standard — Details →
0.6.0-M1 23 Mar 2021 none non-standard — Details →
0.5.4 20 Feb 2021 none non-standard — Details →
0.5.3 06 Nov 2020 none non-standard — Details →
0.5.2 09 Oct 2020 none non-standard — Details →
0.5.1 25 Sep 2020 none non-standard — Details →
0.5.0 11 Sep 2020 none non-standard — Details →
0.5.0-M2 08 Sep 2020 none non-standard — Details →
0.5.0-M1 02 Sep 2020 none non-standard — Details →
0.4.3 31 Aug 2020 none non-standard — Details →
0.4.2 22 Jul 2020 none non-standard — Details →
0.4.2-M1 18 Jul 2020 none non-standard — Details →
0.4.1 29 Apr 2020 none non-standard — Details →
0.4.0 08 Apr 2020 none non-standard — Details →
0.3.8 19 Feb 2020 none non-standard — Details →
0.3.7 09 Jan 2020 none non-standard — Details →
0.3.6 14 Nov 2019 none non-standard — Details →
0.3.5 14 Nov 2019 H1 non-standard Yes Details →
0.3.4 25 Oct 2019 H1 non-standard Yes Details →
0.3.3 19 Aug 2019 H1 non-standard Yes Details →
0.3.3-RC3 17 Aug 2019 H1 non-standard Yes Details →
0.3.3-RC2 09 Aug 2019 H1 non-standard Yes Details →
0.3.3-RC1 06 Aug 2019 H1 non-standard Yes Details →
0.3.2 21 Jun 2019 H1 non-standard Yes Details →
0.3.2-M1 18 Jun 2019 H1 non-standard Yes Details →
0.3.1 01 Jun 2019 H1 non-standard Yes Details →
0.3.1-M1 30 May 2019 H1 non-standard Yes Details →
0.3.0 15 May 2019 H1 non-standard Yes Details →
0.3.0-M1 02 May 2019 H1 non-standard Yes Details →
0.2.5 19 Mar 2019 H1 non-standard Yes Details →
0.2.4 19 Oct 2018 H1 non-standard Yes Details →
0.2.3 20 Aug 2018 H1 non-standard Yes Details →
0.2.2 14 Aug 2018 H1 non-standard Yes Details →
0.2.1 12 Feb 2018 H1 non-standard Yes Details →
0.2.0 29 Jan 2018 H1 non-standard Yes Details →
0.1.6 16 Dec 2017 H1 non-standard Yes Details →
0.1.5 24 Sep 2017 H1 non-standard Yes Details →
0.1.4 11 Sep 2017 H1 non-standard Yes Details →
0.1.3 22 May 2017 H1 non-standard Yes Details →
0.1.2 26 Apr 2017 H1 non-standard Yes Details →
0.1.1 07 Mar 2017 H1 non-standard Yes Details →
0.1.0 09 Jan 2017 H1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.eclipse.milo:sdk-client

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-19135: Insufficient Nonce Validation in Eclipse Milo Client 7.4 high 0.3.6 16 Mar 2020

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 org.eclipse.milo:sdk-client

Is org.eclipse.milo:sdk-client safe to use?

Vulert records 1 vulnerabilities for org.eclipse.milo:sdk-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 org.eclipse.milo:sdk-client's Vulert package health score?

Vulert scores org.eclipse.milo:sdk-client 72/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 org.eclipse.milo:sdk-client affected?

No. 0.6.16, 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 org.eclipse.milo:sdk-client should I use?

0.6.16 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 org.eclipse.milo:sdk-client have?

1 vulnerability is recorded for org.eclipse.milo:sdk-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 org.eclipse.milo:sdk-client vulnerabilities disclosed?

0 vulnerabilities were recorded for org.eclipse.milo:sdk-client in the last 12 months, and the oldest entry in this database dates to 16 Mar 2020. 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 org.eclipse.milo:sdk-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 org.eclipse.milo:sdk-client for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.eclipse.milo:sdk-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.