Is com.h2database:h2 1.3 vulnerable?

Maven · 30 releases from 1.3.146 to 1.3.176 · latest com.h2database:h2 is 2.5.252 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. com.h2database:h2 1.3.176, the last 1.3 release, is affected by 2 known security advisories (2 critical), including CVE-2022-23221, CVE-2021-42392. Upgrade to 2.1.210 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=com.h2database:h2 -DdepVersion=2.1.210 -DforceVersion=true

Is your project on an affected com.h2database:h2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting com.h2database:h2 1.3.176

  • CriticalCVE-2022-23221GHSA-45hx-wfhj-473x21 Jan 2022

    Arbitrary code execution in H2 Console

    Affected
    <2.1.210
    Fixed in
    2.1.210
  • CriticalCVE-2021-42392GHSA-h376-j262-vhq66 Jan 2022

    RCE in H2 Console

    Affected
    >=1.1.100 <2.0.206
    Fixed in
    2.0.206

Every com.h2database:h2 1.3.x release

Affected: 1.3.146 to 1.3.176. Latest com.h2database:h2: 2.5.252.

VersionKnown advisories
com.h2database:h2 1.3.176CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.175CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.174CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.173CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.172CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.171CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.170CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.169CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.168CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.167CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.166CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.165CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.164CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.163CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.162CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.161CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.160CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.159CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.158CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.157CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.156CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.155CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.154CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.153CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.152CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.151CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.150CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.149CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.148CVE-2022-23221, CVE-2021-42392
com.h2database:h2 1.3.146CVE-2022-23221, CVE-2021-42392

Which of your client projects are still on com.h2database:h2 1.3?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact com.h2database:h2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other com.h2database:h2 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.