VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.eclipse.hawkbit:hawkbit-autoconfigure: vulnerability history, versions and safety

org.eclipse.hawkbit:hawkbit-autoconfigure is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 16 releases, first recorded in Apr 2019. 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.hawkbit:hawkbit-autoconfigure vulnerabilities

Vulert verdict on org.eclipse.hawkbit:hawkbit-autoconfigure 1.1.0 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 1.1.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 15 Apr 2019 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Depended on by 9 packages i
  • Stars 606 i
  • Last release 3 months ago i
  • Licence EPL-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 org.eclipse.hawkbit:hawkbit-autoconfigure, 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
1.1.0 03 Jul 2026 none EPL-2.0 — Details →
1.0.4 25 Jun 2026 none EPL-2.0 — Details →
1.0.3 09 Apr 2026 none EPL-2.0 — Details →
1.0.2 07 Apr 2026 none EPL-2.0 — Details →
1.0.1 07 Apr 2026 none EPL-2.0 — Details →
1.0 07 Apr 2026 none EPL-2.0 — Details →
1.0.0 30 Mar 2026 none EPL-2.0 — Details →
0.10.0 09 Mar 2026 none EPL-2.0 — Details →
0.9.0 25 Jun 2025 none EPL-2.0 — Details →
0.8.0 11 Mar 2025 none EPL-2.0 — Details →
0.7.0 14 Jan 2025 none EPL-2.0 — Details →
0.6.1 28 Oct 2024 none EPL-2.0 — Details →
0.5.0 22 Mar 2024 none EPL-2.0 — Details →
0.4.1 11 Jan 2024 none EPL-2.0 — Details →
0.4.0 11 Jan 2024 none EPL-2.0 — Details →
0.3.0 13 Nov 2023 none EPL-2.0 — Details →
0.3.0M9 24 Aug 2023 none non-standard — Details →
0.3.0M8 20 Apr 2023 none non-standard — Details →
0.3.0M7 12 Feb 2021 none non-standard — Details →
0.3.0M6 17 Jan 2020 none non-standard — Details →
0.3.0M5 29 Jul 2019 none non-standard — Details →
0.3.0M4 06 Jun 2019 none non-standard — Details →
0.3.0M3 21 May 2019 none non-standard — Details →
0.3.0M2 02 Apr 2019 none non-standard — Details →
0.3.0M1 02 Feb 2019 H1 non-standard Yes Details →
0.2.5 30 Nov 2018 H1 non-standard Yes Details →
0.2.4 25 Oct 2018 H1 non-standard Yes Details →
0.2.3 01 Oct 2018 H1 non-standard Yes Details →
0.2.2 20 Sep 2018 H1 non-standard Yes Details →
0.2.1 05 Jul 2018 H1 non-standard Yes Details →
0.2.0 07 Jun 2018 H1 non-standard Yes Details →
0.2.0M9 14 May 2018 H1 non-standard Yes Details →
0.2.0M8 27 Mar 2018 H1 non-standard Yes Details →
0.2.0M7 15 Mar 2018 H1 non-standard Yes Details →
0.2.0M6 09 Mar 2018 H1 non-standard Yes Details →
0.2.0M5 02 Mar 2018 H1 non-standard Yes Details →
0.2.0M4 30 Oct 2017 H1 non-standard Yes Details →
0.2.0M3 03 Apr 2017 H1 non-standard Yes Details →
0.2.0M2 07 Oct 2016 H1 Apache-2.0 Yes Details →
0.2.0M1 06 Oct 2016 H1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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.hawkbit:hawkbit-autoconfigure

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-10240: Cleartext Transmission of Sensitive Information in Eclipse hawkBit 8.1 high 0.3.0M2 15 Apr 2019

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.hawkbit:hawkbit-autoconfigure

Is org.eclipse.hawkbit:hawkbit-autoconfigure safe to use?

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

Vulert scores org.eclipse.hawkbit:hawkbit-autoconfigure 83/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.hawkbit:hawkbit-autoconfigure affected?

No. 1.1.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 org.eclipse.hawkbit:hawkbit-autoconfigure should I use?

1.1.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 org.eclipse.hawkbit:hawkbit-autoconfigure have?

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

0 vulnerabilities were recorded for org.eclipse.hawkbit:hawkbit-autoconfigure in the last 12 months, and the oldest entry in this database dates to 15 Apr 2019. 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.hawkbit:hawkbit-autoconfigure 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.hawkbit:hawkbit-autoconfigure for upcoming vulnerabilities?

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