Is com.h2database:h2 1.4 vulnerable?
Maven · 24 releases from 1.4.177 to 1.4.200 · latest com.h2database:h2 is 2.5.252 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. com.h2database:h2 1.4.200, the last 1.4 release, is affected by 4 known security advisories (2 critical, 2 high), including CVE-2022-23221, CVE-2021-42392, CVE-2022-45868. Upgrade to 2.2.220 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=com.h2database:h2 -DdepVersion=2.2.220 -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.4.200
Password exposure in H2 Database
- Affected
- >=1.4.198 <2.2.220
- Fixed in
- 2.2.220
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
Improper Restriction of XML External Entity Reference in com.h2database:h2.
- Affected
- >=1.4.198 <2.0.202
- Fixed in
- 2.0.202
Every com.h2database:h2 1.4.x release
Affected: 1.4.177 to 1.4.200. Latest com.h2database:h2: 2.5.252.
| Version | Known advisories |
|---|---|
| com.h2database:h2 1.4.200 | CVE-2022-45868, CVE-2022-23221, CVE-2021-42392, CVE-2021-23463 |
| com.h2database:h2 1.4.199 | CVE-2022-45868, CVE-2022-23221, CVE-2021-42392, CVE-2021-23463 |
| com.h2database:h2 1.4.198 | CVE-2022-45868, CVE-2022-23221, CVE-2021-42392, CVE-2021-23463 |
| com.h2database:h2 1.4.197 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.196 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.195 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.194 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.193 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.192 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.191 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.190 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.189 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.188 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.187 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.186 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.185 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.184 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.183 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.182 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.181 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.180 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.179 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.178 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.4.177 | CVE-2022-23221, CVE-2021-42392 |
Which of your client projects are still on com.h2database:h2 1.4?
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.