Is com.h2database:h2 1.2 vulnerable?
Maven · 27 releases from 1.2.120 to 1.2.147 · latest com.h2database:h2 is 2.5.252 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. com.h2database:h2 1.2.147, the last 1.2 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.
mvn versions:use-dep-version -Dincludes=com.h2database:h2 -DdepVersion=2.1.210 -DforceVersion=trueIs your project on an affected com.h2database:h2?
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.2.147
Arbitrary code execution in H2 Console
- Affected
- <2.1.210
- Fixed in
- 2.1.210
RCE in H2 Console
- Affected
- >=1.1.100 <2.0.206
- Fixed in
- 2.0.206
Every com.h2database:h2 1.2.x release
Affected: 1.2.120 to 1.2.147. Latest com.h2database:h2: 2.5.252.
| Version | Known advisories |
|---|---|
| com.h2database:h2 1.2.147 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.145 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.144 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.143 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.142 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.141 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.140 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.139 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.138 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.137 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.136 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.135 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.134 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.133 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.132 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.131 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.130 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.129 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.128 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.127 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.126 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.125 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.124 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.123 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.122 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.121 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.2.120 | CVE-2022-23221, CVE-2021-42392 |
Which of your client projects are still on com.h2database:h2 1.2?
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.