VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.hsqldb:hsqldb: vulnerability history, versions and safety

org.hsqldb:hsqldb is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 22 releases, first recorded in Oct 2022. 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
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.hsqldb:hsqldb vulnerabilities

Vulert verdict on org.hsqldb:hsqldb 2.7.4 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 2.7.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 06 Oct 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 365 packages i
  • Last release 23 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 org.hsqldb:hsqldb, 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
2.7.4 03 Nov 2024 none non-standard — Details →
2.7.3 31 May 2024 none non-standard — Details →
2.7.2 31 May 2023 none non-standard — Details →
2.7.1 22 Oct 2022 none non-standard — Details →
2.7.0 26 Jul 2022 C1 non-standard Yes Details →
2.6.1 25 Oct 2021 C1 non-standard Yes Details →
2.5.2 12 Apr 2021 C1 non-standard Yes Details →
2.6.0 08 Apr 2021 C1 non-standard Yes Details →
2.5.1 28 Jun 2020 C1 non-standard Yes Details →
2.5.0 03 Jun 2019 C1 non-standard Yes Details →
2.3.6 20 May 2018 C1 non-standard Yes Details →
2.4.1 20 May 2018 C1 non-standard Yes Details →
2.3.5 16 Apr 2017 C1 non-standard Yes Details →
2.4.0 09 Apr 2017 C1 non-standard Yes Details →
2.3.4 16 May 2016 C1 non-standard Yes Details →
2.3.3 01 Jul 2015 C1 non-standard Yes Details →
2.3.2 14 Feb 2014 C1 non-standard Yes Details →
2.3.1 08 Oct 2013 C1 non-standard Yes Details →
2.3.0 18 Jul 2013 C1 non-standard Yes Details →
2.2.9 12 Oct 2012 C1 non-standard Yes Details →
2.2.8 22 Jan 2012 C1 non-standard Yes Details →
2.2.7 15 Jan 2012 C1 non-standard Yes Details →
2.2.6 20 Nov 2011 C1 non-standard Yes Details →
2.2.4 13 Jun 2011 C1 non-standard Yes Details →
2.0.0 08 Jun 2010 C1 non-standard Yes Details →
1.8.0.10 24 Apr 2009 C1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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.hsqldb:hsqldb

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-41853: HyperSQL DataBase Remote Code Execution 9.8 critical 2.7.1 06 Oct 2022

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.hsqldb:hsqldb

Is org.hsqldb:hsqldb safe to use?

Vulert records 1 vulnerabilities for org.hsqldb:hsqldb in Maven: 1 critical, 0 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.hsqldb:hsqldb's Vulert package health score?

Vulert scores org.hsqldb:hsqldb 81/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.hsqldb:hsqldb affected?

No. 2.7.4, 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.hsqldb:hsqldb should I use?

2.7.4 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.hsqldb:hsqldb have?

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

0 vulnerabilities were recorded for org.hsqldb:hsqldb in the last 12 months, and the oldest entry in this database dates to 06 Oct 2022. 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.hsqldb:hsqldb 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.hsqldb:hsqldb for upcoming vulnerabilities?

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