VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.github.oshi:oshi-core: vulnerability history, versions and safety

com.github.oshi:oshi-core is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

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 com.github.oshi:oshi-core vulnerabilities

Vulert verdict on com.github.oshi:oshi-core 7.7.2 i

Updated on 23 Oct 2026

Good news: 7.7.2, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 7.7.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 5,271 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT 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 com.github.oshi:oshi-core, 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
7.7.2 21 Oct 2026 none MIT — Details →
7.7.1 10 Oct 2026 none MIT — Details →
7.7.0 29 Sep 2026 none MIT — Details →
7.6.1 01 Sep 2026 none MIT — Details →
7.6.0 23 Aug 2026 none MIT — Details →
7.5.0 17 Aug 2026 none MIT — Details →
7.4.4 06 Aug 2026 none MIT — Details →
7.4.3 31 Jul 2026 none MIT — Details →
7.4.2 24 Jul 2026 none MIT — Details →
7.4.1 18 Jul 2026 none MIT — Details →
7.4.0 08 Jul 2026 none MIT — Details →
7.3.2 26 Jun 2026 none MIT — Details →
7.3.1 12 Jun 2026 none MIT — Details →
7.3.0 06 Jun 2026 none MIT — Details →
7.2.1 25 May 2026 none MIT — Details →
7.2.0 24 May 2026 none MIT — Details →
7.1.0 07 May 2026 none MIT — Details →
7.0.1 02 May 2026 none MIT — Details →
7.0.0 30 Apr 2026 none MIT — Details →
6.12.0 21 Apr 2026 none MIT — Details →
6.11.1 08 Apr 2026 none MIT — Details →
6.11.0 04 Apr 2026 none MIT — Details →
6.10.0 22 Feb 2026 none MIT — Details →
6.9.3 29 Jan 2026 none MIT — Details →
6.9.2 20 Dec 2025 none MIT — Details →
6.9.1 19 Oct 2025 none MIT — Details →
6.9.0 19 Sep 2025 none MIT — Details →
6.8.3 17 Aug 2025 none MIT — Details →
6.8.2 31 May 2025 none non-standard — Details →
6.8.1 15 Apr 2025 none non-standard — Details →
6.8.0 22 Mar 2025 none non-standard — Details →
6.7.1 13 Mar 2025 none non-standard — Details →
6.7.0 26 Feb 2025 none non-standard — Details →
6.6.6 25 Jan 2025 none non-standard — Details →
6.6.5 28 Sep 2024 none non-standard — Details →
6.6.4 15 Sep 2024 none non-standard — Details →
6.6.3 20 Aug 2024 none non-standard — Details →
6.6.2 22 Jul 2024 none non-standard — Details →
6.6.1 26 May 2024 none non-standard — Details →
6.6.0 13 Apr 2024 none non-standard — Details →
6.5.0 10 Mar 2024 none non-standard — Details →
6.4.13 26 Feb 2024 none non-standard — Details →
6.4.12 10 Feb 2024 none non-standard — Details →
6.4.11 11 Jan 2024 none non-standard — Details →
6.4.10 24 Dec 2023 none non-standard — Details →
6.4.9 10 Dec 2023 none non-standard — Details →
6.4.8 24 Nov 2023 none non-standard — Details →
6.4.7 02 Nov 2023 none non-standard — Details →
6.4.6 25 Sep 2023 none non-standard — Details →
6.4.5 21 Aug 2023 none non-standard — Details →
6.4.4 02 Jul 2023 none non-standard — Details →
6.4.3 06 Jun 2023 none non-standard — Details →
6.4.2 03 May 2023 none non-standard — Details →
6.4.1 18 Mar 2023 none non-standard — Details →
6.4.0 03 Dec 2022 none non-standard — Details →
6.3.2 17 Nov 2022 none non-standard — Details →
6.3.1 30 Oct 2022 none non-standard — Details →
6.3.0 17 Oct 2022 none non-standard — Details →
6.2.2 21 Jul 2022 none non-standard — Details →
6.2.1 29 Jun 2022 none non-standard — Details →
6.2.0 26 Jun 2022 none non-standard — Details →
6.1.6 11 Apr 2022 none non-standard — Details →
6.1.5 15 Mar 2022 none non-standard — Details →
6.1.4 01 Mar 2022 none non-standard — Details →
6.1.3 22 Feb 2022 none MIT — Details →
6.1.2 14 Feb 2022 none MIT — Details →
6.1.1 13 Feb 2022 none MIT — Details →
6.1.0 20 Jan 2022 none MIT — Details →
6.0.0 01 Jan 2022 none MIT — Details →
5.8.7 31 Dec 2021 none MIT — Details →
5.8.6 15 Dec 2021 none MIT — Details →
5.8.5 25 Nov 2021 none MIT — Details →
5.8.4 25 Nov 2021 none MIT — Details →
3.14.0 15 Nov 2021 none MIT — Details →
5.8.3 21 Oct 2021 none MIT — Details →
5.8.2 05 Sep 2021 none MIT — Details →
5.8.1 23 Aug 2021 none MIT — Details →
5.8.0 18 Jul 2021 none MIT — Details →
5.7.5 12 Jun 2021 none MIT — Details →
5.7.4 30 May 2021 none MIT — Details →
5.7.3 16 May 2021 none MIT — Details →
5.7.2 02 May 2021 none MIT — Details →
5.7.1 16 Apr 2021 none MIT — Details →
5.7.0 01 Apr 2021 none MIT — Details →
5.6.1 22 Mar 2021 none MIT — Details →
5.6.0 02 Mar 2021 none MIT — Details →
5.5.1 21 Feb 2021 none MIT — Details →
5.5.0 09 Feb 2021 none MIT — Details →
5.4.1 24 Jan 2021 none MIT — Details →
5.4.0 18 Jan 2021 none MIT — Details →
5.3.7 20 Dec 2020 none MIT — Details →
5.3.6 15 Nov 2020 none MIT — Details →
5.3.5 11 Nov 2020 none MIT — Details →
5.3.4 01 Nov 2020 none MIT — Details →
5.3.3 29 Oct 2020 none MIT — Details →
5.3.2 25 Oct 2020 none MIT — Details →
5.3.1 18 Oct 2020 none MIT — Details →
5.3.0 11 Oct 2020 none MIT — Details →
5.2.5 30 Aug 2020 none MIT — Details →
4.9.5 30 Aug 2020 none MIT — Details →
5.2.4 16 Aug 2020 none — — Details →
4.9.4 16 Aug 2020 none — — Details →
5.2.3 09 Aug 2020 none — — Details →
4.9.3 09 Aug 2020 none — — Details →
5.2.2 20 Jul 2020 none — — Details →
4.9.2 20 Jul 2020 none — — Details →
5.2.1 15 Jul 2020 none — — Details →
4.9.1 15 Jul 2020 none — — Details →
3.13.6 15 Jul 2020 none — — Details →
5.2.0 26 Jun 2020 none — — Details →
4.9.0 26 Jun 2020 none — — Details →
5.1.2 07 Jun 2020 none — — Details →
4.8.2 07 Jun 2020 none — — Details →
5.1.1 31 May 2020 none — — Details →
4.8.1 31 May 2020 none — — Details →
5.1.0 20 May 2020 none — — Details →
4.8.0 20 May 2020 none — — Details →
5.0.2 14 May 2020 none — — Details →
4.7.3 14 May 2020 none — — Details →
5.0.1 06 May 2020 none — — Details →

The newest 120 of 171 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for com.github.oshi:oshi-core

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 com.github.oshi:oshi-core

Is com.github.oshi:oshi-core safe to use?

Vulert has no vulnerabilities on record for com.github.oshi:oshi-core in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is com.github.oshi:oshi-core's Vulert package health score?

Vulert scores com.github.oshi:oshi-core 84/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 com.github.oshi:oshi-core affected?

No. 7.7.2, 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 com.github.oshi:oshi-core have?

0 vulnerabilities are recorded for com.github.oshi:oshi-core in the Maven ecosystem: 0 critical, 0 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 com.github.oshi:oshi-core vulnerabilities disclosed?

0 vulnerabilities were recorded for com.github.oshi:oshi-core in the last 12 months. 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 com.github.oshi:oshi-core 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 com.github.oshi:oshi-core for upcoming vulnerabilities?

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