VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

tech.kwik:kwik: vulnerability history, versions and safety

tech.kwik:kwik is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 14 releases, from May 2024 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
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 tech.kwik:kwik vulnerabilities

Vulert verdict on tech.kwik:kwik 0.12.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.12.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 20 Feb 2025 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Stars 505 i
  • Last release this month i
  • Licence LGPL-3.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 tech.kwik:kwik, 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.12.1 18 Oct 2026 none LGPL-3.0 — Details →
0.12 07 Oct 2026 none LGPL-3.0 — Details →
0.11 11 Jul 2026 none LGPL-3.0 — Details →
0.10.10 22 May 2026 none LGPL-3.0 — Details →
0.10.9 18 Apr 2026 none LGPL-3.0 — Details →
0.10.8 18 Nov 2025 none LGPL-3.0 — Details →
0.10.7 30 Oct 2025 none LGPL-3.0 — Details →
0.10.6 06 Sep 2025 none LGPL-3.0 — Details →
0.10.5 31 Aug 2025 none LGPL-3.0 — Details →
0.10.4 20 Jul 2025 none LGPL-3.0 — Details →
0.10.3 03 Jun 2025 none LGPL-3.0 — Details →
0.10.2 25 Apr 2025 none LGPL-3.0 — Details →
0.10.1 16 Feb 2025 none LGPL-3.0 — Details →
0.10 10 Jan 2025 M1 LGPL-3.0 Yes Details →
0.9.1 14 Nov 2024 M1 LGPL-3.0 Yes Details →
0.9 04 Nov 2024 M1 LGPL-3.0 Yes Details →
0.8.13 02 Jul 2024 M1 LGPL-3.0 Yes Details →
0.8.12 22 Jun 2024 M1 LGPL-3.0 Yes Details →
0.8.11 28 May 2024 M1 LGPL-3.0 Yes Details →
0.8.10 03 Mar 2024 M1 LGPL-3.0 Yes Details →
0.8.9 01 Jan 2024 M1 LGPL-3.0 Yes Details →
0.8.8 29 Dec 2023 M1 LGPL-3.0 Yes Details →
0.8.7 19 Dec 2023 M1 LGPL-3.0 Yes Details →
0.8.6 16 Dec 2023 M1 LGPL-3.0 Yes Details →
0.8.5 12 Dec 2023 M1 LGPL-3.0 Yes Details →
0.8.4 02 Dec 2023 M1 LGPL-3.0 Yes Details →
0.8.3 06 Nov 2023 M1 LGPL-3.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for tech.kwik:kwik

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-22588: Kwik does not discard unused encryption keys 5.3 medium 0.8 24 May 2024
CVE-2025-23020: Kwik Package Hash Collision Vulnerability Leading to DoS Attack 5.3 medium 0.10.1 20 Feb 2025

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 tech.kwik:kwik

Is tech.kwik:kwik safe to use?

Vulert records 2 vulnerabilities for tech.kwik:kwik in Maven: 0 critical, 0 high, 2 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 tech.kwik:kwik's Vulert package health score?

Vulert scores tech.kwik:kwik 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 tech.kwik:kwik affected?

No. 0.12.1, 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 tech.kwik:kwik have?

2 vulnerabilities are recorded for tech.kwik:kwik in the Maven ecosystem: 0 critical, 0 high, 2 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 tech.kwik:kwik vulnerabilities disclosed?

0 vulnerabilities were recorded for tech.kwik:kwik in the last 12 months, and the oldest entry in this database dates to 24 May 2024. 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 tech.kwik:kwik 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 tech.kwik:kwik for upcoming vulnerabilities?

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