VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.github.luben:zstd-jni: vulnerability history, versions and safety

com.github.luben:zstd-jni 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.luben:zstd-jni vulnerabilities

Vulert verdict on com.github.luben:zstd-jni 1.5.7-24 i

Updated on 23 Oct 2026

Good news: 1.5.7-24, the version you would install today, has no known vulnerabilities.

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

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

  • Current release 1.5.7-24 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 34 packages i
  • Last release this month i
  • Licence BSD-2-Clause 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.luben:zstd-jni, 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.5.7-24 19 Oct 2026 none BSD-2-Clause — Details →
1.5.7-23 10 Oct 2026 none BSD-2-Clause — Details →
1.5.7-22 06 Oct 2026 none BSD-2-Clause — Details →
1.5.7-21 03 Oct 2026 none BSD-2-Clause — Details →
1.5.7-20 24 Sep 2026 none BSD-2-Clause — Details →
1.5.7-19 22 Sep 2026 none BSD-2-Clause — Details →
1.5.7-18 20 Sep 2026 none BSD-2-Clause — Details →
1.5.7-17 16 Sep 2026 none BSD-2-Clause — Details →
1.5.7-16 29 Aug 2026 none BSD-2-Clause — Details →
1.5.7-15 16 Aug 2026 none BSD-2-Clause — Details →
1.5.7-14 16 Aug 2026 none BSD-2-Clause — Details →
1.5.7-13 08 Aug 2026 none BSD-2-Clause — Details →
1.5.7-12 26 Jul 2026 none BSD-2-Clause — Details →
1.5.7-11 13 Jun 2026 none BSD-2-Clause — Details →
1.5.7-10 03 Jun 2026 none BSD-2-Clause — Details →
1.5.7-9 20 May 2026 none BSD-2-Clause — Details →
1.5.7-8 01 May 2026 none BSD-2-Clause — Details →
1.5.7-7 04 Feb 2026 none BSD-2-Clause — Details →
1.5.7-6 21 Oct 2025 none BSD-2-Clause — Details →
1.5.7-5 02 Oct 2025 none BSD-2-Clause — Details →
1.5.7-4 02 Jul 2025 none BSD-2-Clause — Details →
1.5.7-3 03 May 2025 none BSD-2-Clause — Details →
1.5.7-2 17 Mar 2025 none BSD-2-Clause — Details →
1.5.7-1 20 Feb 2025 none BSD-2-Clause — Details →
1.5.6-10 09 Feb 2025 none BSD-2-Clause — Details →
1.5.6-9 01 Jan 2025 none BSD-2-Clause — Details →
1.5.6-8 24 Nov 2024 none BSD-2-Clause — Details →
1.5.6-7 28 Oct 2024 none BSD-2-Clause — Details →
1.5.6-6 22 Sep 2024 none BSD-2-Clause — Details →
1.5.6-5 29 Aug 2024 none BSD-2-Clause — Details →
1.5.6-4 20 Jul 2024 none BSD-2-Clause — Details →
1.5.6-3 24 Apr 2024 none BSD-2-Clause — Details →
1.5.6-2 04 Apr 2024 none BSD-2-Clause — Details →
1.5.6-1 27 Mar 2024 none BSD-2-Clause — Details →
1.5.5-11 01 Dec 2023 none BSD-2-Clause — Details →
1.5.5-10 01 Nov 2023 none BSD-2-Clause — Details →
1.5.5-9 31 Oct 2023 none BSD-2-Clause — Details →
1.5.5-8 31 Oct 2023 none BSD-2-Clause — Details →
1.5.5-7 29 Oct 2023 none BSD-2-Clause — Details →
1.5.5-6 01 Oct 2023 none BSD-2-Clause — Details →
1.5.5-5 16 Jul 2023 none BSD-2-Clause — Details →
1.5.5-4 05 Jun 2023 none BSD-2-Clause — Details →
1.5.5-3 20 May 2023 none BSD-2-Clause — Details →
1.5.5-2 22 Apr 2023 none BSD-2-Clause — Details →
1.5.5-1 05 Apr 2023 none BSD-2-Clause — Details →
1.5.4-2 28 Feb 2023 none BSD-2-Clause — Details →
1.5.4-1 10 Feb 2023 none BSD-2-Clause — Details →
1.5.2-5 18 Oct 2022 none BSD-2-Clause — Details →
1.5.2-4 11 Sep 2022 none BSD-2-Clause — Details →
1.5.2-3 12 May 2022 none BSD-2-Clause — Details →
1.5.2-2 22 Feb 2022 none BSD-2-Clause — Details →
1.5.2-1 22 Jan 2022 none BSD-2-Clause — Details →
1.5.1-1 23 Dec 2021 none BSD-2-Clause — Details →
1.5.0-5 14 Dec 2021 none BSD-2-Clause — Details →
1.5.0-4 21 Jul 2021 none BSD-2-Clause — Details →
1.5.0-3 19 Jul 2021 none BSD-2-Clause — Details →
1.5.0-2 09 Jun 2021 none BSD-2-Clause — Details →
1.5.0-1 06 Jun 2021 none BSD-2-Clause — Details →
1.4.9-5 14 Apr 2021 none BSD-2-Clause — Details →
1.4.9-4 05 Apr 2021 none BSD-2-Clause — Details →
1.4.9-3 05 Apr 2021 none BSD-2-Clause — Details →
1.4.9-2 29 Mar 2021 none BSD-2-Clause — Details →
1.4.9-1 08 Mar 2021 none BSD-2-Clause — Details →
1.4.8-7 02 Mar 2021 none BSD-2-Clause — Details →
1.4.8-6 27 Feb 2021 none BSD-2-Clause — Details →
1.4.8-5 22 Feb 2021 none BSD-2-Clause — Details →
1.4.8-4 09 Feb 2021 none BSD-2-Clause — Details →
1.4.8-3 31 Jan 2021 none BSD-2-Clause — Details →
1.4.8-2 24 Jan 2021 none BSD-2-Clause — Details →
1.4.8-1 19 Dec 2020 none BSD-2-Clause — Details →
1.4.7-3 18 Dec 2020 none BSD-2-Clause — Details →
1.4.7-2 18 Dec 2020 none BSD-2-Clause — Details →
1.4.7-1 18 Dec 2020 none BSD-2-Clause — Details →
1.4.5-12 30 Oct 2020 none BSD-2-Clause — Details →
1.4.5-11 27 Oct 2020 none BSD-2-Clause — Details →
1.4.5-10 26 Oct 2020 none BSD-2-Clause — Details →
1.4.5-9 26 Oct 2020 none BSD-2-Clause — Details →
1.4.5-8 24 Oct 2020 none BSD-2-Clause — Details →
1.4.5-7 18 Oct 2020 none BSD-2-Clause — Details →
1.4.5-6 21 Jul 2020 none BSD-2-Clause — Details →
1.4.5-5 02 Jul 2020 none BSD-2-Clause — Details →
1.4.5-4 05 Jun 2020 none BSD-2-Clause — Details →
1.4.5-3 03 Jun 2020 none BSD-2-Clause — Details →
1.4.5-2 30 May 2020 none BSD-2-Clause — Details →
1.4.5-1 29 May 2020 none BSD-2-Clause — Details →
1.4.4-11 08 May 2020 none BSD-2-Clause — Details →
1.4.4-10 06 May 2020 none BSD-2-Clause — Details →
1.4.4-9 27 Mar 2020 none BSD-2-Clause — Details →
1.4.4-8 27 Mar 2020 none BSD-2-Clause — Details →
1.4.4-7 24 Jan 2020 none BSD-2-Clause — Details →
1.4.4-6 22 Jan 2020 none BSD-2-Clause — Details →
1.4.4-5 21 Jan 2020 none BSD-2-Clause — Details →
1.4.4-4 15 Jan 2020 none BSD-2-Clause — Details →
1.4.4-3 21 Nov 2019 none BSD-2-Clause — Details →
1.4.4-2 06 Nov 2019 none BSD-2-Clause — Details →
1.4.4-1 05 Nov 2019 none BSD-2-Clause — Details →
1.4.3-1 20 Aug 2019 none BSD-2-Clause — Details →
1.4.2-1 27 Jul 2019 none BSD-2-Clause — Details →
1.4.1-1 24 Jul 2019 none BSD-2-Clause — Details →
1.4.0-1 17 Apr 2019 none BSD-2-Clause — Details →
1.3.8-9 15 Apr 2019 none — — Details →
1.3.8-8 12 Apr 2019 none — — Details →
1.3.8-7 12 Apr 2019 none — — Details →
1.3.8-6 03 Mar 2019 none — — Details →
1.3.8-5 22 Feb 2019 none — — Details →
1.3.8-4 14 Feb 2019 none — — Details →
1.3.8-3 29 Jan 2019 none — — Details →
1.3.8-2 29 Jan 2019 none — — Details →
1.3.8-1 09 Jan 2019 none — — Details →
1.3.7-3 05 Dec 2018 none — — Details →
1.3.7-2 19 Nov 2018 none — — Details →
1.3.7-1 22 Oct 2018 none — — Details →
1.3.6-1 07 Oct 2018 none — — Details →
1.3.5-4 17 Sep 2018 none — — Details →
1.3.5-3 11 Aug 2018 none — — Details →
1.3.5-2 05 Jul 2018 none — — Details →
1.3.5-1 29 Jun 2018 none — — Details →
1.3.4-11 22 Jun 2018 none — — Details →
1.3.4-10 01 Jun 2018 none — — Details →
1.3.4-9 01 Jun 2018 none — — Details →

The newest 120 of 163 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.luben:zstd-jni

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.luben:zstd-jni

Is com.github.luben:zstd-jni safe to use?

Vulert has no vulnerabilities on record for com.github.luben:zstd-jni 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.luben:zstd-jni's Vulert package health score?

Vulert scores com.github.luben:zstd-jni 89/100, which reads as healthy. 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.luben:zstd-jni affected?

No. 1.5.7-24, 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.luben:zstd-jni have?

0 vulnerabilities are recorded for com.github.luben:zstd-jni 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.luben:zstd-jni vulnerabilities disclosed?

0 vulnerabilities were recorded for com.github.luben:zstd-jni 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.luben:zstd-jni 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.luben:zstd-jni for upcoming vulnerabilities?

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