Is com.h2database:h2 2.0 vulnerable?
Maven · 3 releases from 2.0.202 to 2.0.206 · latest com.h2database:h2 is 2.5.252 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. com.h2database:h2 2.0.206, the last 2.0 release, is affected by 2 known security advisories (1 critical, 1 high), including CVE-2022-23221, CVE-2022-45868. 1 more affects earlier 2.0.x releases. 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 2.0.206
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
Fixed within 2.0.x, affecting earlier releases
RCE in H2 Console
- Affected
- >=1.1.100 <2.0.206
- Fixed in
- 2.0.206
Every com.h2database:h2 2.0.x release
Affected: 2.0.202 to 2.0.206. Latest com.h2database:h2: 2.5.252.
| Version | Known advisories |
|---|---|
| com.h2database:h2 2.0.206 | CVE-2022-45868, CVE-2022-23221 |
| com.h2database:h2 2.0.204 | CVE-2022-45868, CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 2.0.202 | CVE-2022-45868, CVE-2022-23221, CVE-2021-42392 |
Which of your client projects are still on com.h2database:h2 2.0?
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.