VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.github:hyavijava: vulnerability history, versions and safety

com.github:hyavijava is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 5 releases, first recorded in Dec 2023. 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 C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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:hyavijava vulnerabilities

Vulert verdict on com.github:hyavijava 6.0.08.1 i

Updated on 23 Oct 2026

Careful: 6.0.08.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 52/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.0.08.1 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 27 Dec 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 5 i
  • OpenSSF scorecard 3/10 i
  • Last release 21 months ago i
  • Licence non-standard 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:hyavijava, 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
6.0.08.1 04 Jan 2025 C1 non-standard No Details →
6.0.07.1 14 Mar 2023 C1 non-standard No Details →
6.0.05.1 31 Aug 2021 C1 non-standard No Details →
1.0.1 27 Aug 2021 C1 non-standard No Details →
1.0.0 14 Oct 2020 C1 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 com.github:hyavijava

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-51084: hyavijava stack overflow vulnerability 9.8 critical No fix published 27 Dec 2023

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:hyavijava

Is com.github:hyavijava safe to use?

Vulert records 1 vulnerabilities for com.github:hyavijava in Maven: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is com.github:hyavijava's Vulert package health score?

Vulert scores com.github:hyavijava 52/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of com.github:hyavijava affected?

Yes. 6.0.08.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of com.github:hyavijava should I use?

6.0.08.1 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 com.github:hyavijava have?

1 vulnerability is recorded for com.github:hyavijava in the Maven ecosystem: 1 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:hyavijava vulnerabilities disclosed?

0 vulnerabilities were recorded for com.github:hyavijava in the last 12 months, and the oldest entry in this database dates to 27 Dec 2023. 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:hyavijava 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:hyavijava for upcoming vulnerabilities?

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