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.
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.3.176
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.3.x release
Affected: 1.3.146 to 1.3.176. Latest com.h2database:h2: 2.5.252.
| Version | Known advisories |
|---|---|
| com.h2database:h2 1.3.176 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.175 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.174 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.173 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.172 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.171 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.170 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.169 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.168 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.167 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.166 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.165 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.164 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.163 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.162 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.161 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.160 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.159 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.158 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.157 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.156 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.155 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.154 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.153 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.152 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.151 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.150 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.149 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.148 | CVE-2022-23221, CVE-2021-42392 |
| com.h2database:h2 1.3.146 | CVE-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.