CVE-2022-23221

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 26.6%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 65%
CISA-KEV: Not listedEPSS: 65%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

H2 Console before 2.1.210 allows remote attackers to execute arbitrary code via a jdbc:h2:mem JDBC URL containing the IGNORE_UNKNOWN_SETTINGS=TRUE;FORBID_CREATION=FALSE;INIT=RUNSCRIPT substring, a different vulnerability than CVE-2021-42392.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.2%
KEV
Not listed

Published

January 19, 2022

Last Modified

May 5, 2025

Advisory Details (8)

Auto-updated Jun 9, 2026
Patch available. Sources: github, github_release.
generic

[SECURITY] [DSA 5076-1] h2database security update

https://www.debian.org/security/2022/dsa-5076
generic
https://twitter.com/d0nkey_man/status/1483824727936450564
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20230818-0011/
generic Patch Available

[SECURITY] [DLA 2923-1] h2database security update

https://lists.debian.org/debian-lts-announce/2022/02/msg00017.html
github

Security Advisories · h2database/h2database · GitHub

https://github.com/h2database/h2database/security/advisories
github_release Patch Available

Version 2.1.210

Patch available: h2database/h2database version-2.1.210

https://github.com/h2database/h2database/releases/tag/version-2.1.210
generic

Full Disclosure: Unauthenticated RCE vuln in the H2 Database console: CVE-2022-23221.

http://seclists.org/fulldisclosure/2022/Jan/39
generic

Packet Storm

http://packetstormsecurity.com/files/165676/H2-Database-Console-Remote-Code-Execution.html

Vendor Advisories for CVE-2022-23221(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibh2-java-doc (1.4.197-4+deb10u1build0.21.10.1) @ impish2026-05-26ubuntu
ubuntulibh2-java-doc (1.4.191-1ubuntu0.1~esm1) @ xenial2026-05-26ubuntu
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhateap7-h2database-0:1.4.197-2.redhat_00005.1.ep7.el72024-11-25redhat
redhath22022-07-07redhat
redhateap7-h2database-0:1.4.197-2.redhat_00004.1.el8eap2022-06-06redhat
redhateap7-h2database-0:1.4.197-2.redhat_00004.1.el7eap2022-06-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.h2database:h21.0.20061217 ... 2.0.206 (131 versions)2.1.210—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-09 19:07 UTCEPSS rescore
  3. 2026-07-08 15:12 UTCEPSS rescore
  4. 2026-07-05 02:28 UTCEPSS rescore
  5. 2026-07-01 15:04 UTCEPSS rescore
  6. 2026-06-29 22:44 UTCOSV refresh
  7. 2026-06-28 14:06 UTCEPSS rescore
  8. 2026-06-27 03:07 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-24 14:03 UTCEPSS rescore
  11. 2026-06-24 14:03 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-21 01:58 UTCEPSS rescore
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-18 17:51 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-17 17:51 UTCEPSS rescore
  19. 2026-06-17 17:51 UTCEPSS rescore
  20. 2026-06-16 17:51 UTCEPSS rescore
  21. 2026-06-15 17:46 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-14 23:15 UTCEPSS rescore
  24. 2026-06-12 23:10 UTCEPSS rescore
  25. 2026-06-12 23:10 UTCEPSS rescore
Show 33 more
  1. 2026-06-12 11:10 UTCOSV refresh
  2. 2026-06-11 13:58 UTCEPSS rescore
  3. 2026-06-11 13:58 UTCEPSS rescore
  4. 2026-06-10 22:16 UTCEPSS rescore
  5. 2026-06-10 13:20 UTCEPSS rescore
  6. 2026-06-07 15:23 UTCEPSS rescore
  7. 2026-06-07 15:23 UTCEPSS rescore
  8. 2026-06-06 13:46 UTCEPSS rescore
  9. 2026-06-06 13:46 UTCEPSS rescore
  10. 2026-06-05 22:45 UTCEPSS rescore
  11. 2026-06-04 13:11 UTCEPSS rescore
  12. 2026-06-04 13:11 UTCEPSS rescore
  13. 2026-06-02 20:11 UTCEPSS rescore
  14. 2026-06-02 20:11 UTCEPSS rescore
  15. 2026-06-02 20:11 UTCEPSS rescore
  16. 2026-06-01 13:50 UTCEPSS rescore
  17. 2026-06-01 13:50 UTCEPSS rescore
  18. 2026-06-01 13:50 UTCEPSS rescore
  19. 2026-05-31 22:29 UTCEPSS rescore
  20. 2026-05-31 22:29 UTCEPSS rescore
  21. 2026-05-31 00:15 UTCEPSS rescore
  22. 2026-05-31 00:15 UTCEPSS rescore
  23. 2026-05-29 13:42 UTCEPSS rescore
  24. 2026-05-28 13:43 UTCEPSS rescore
  25. 2026-05-28 13:43 UTCEPSS rescore
  26. 2026-05-28 13:43 UTCEPSS rescore
  27. 2026-05-27 13:39 UTCEPSS rescore
  28. 2026-05-27 13:39 UTCEPSS rescore
  29. 2026-05-26 13:43 UTCEPSS rescore
  30. 2026-05-26 07:17 UTCEPSS rescore
  31. 2026-05-26 07:17 UTCEPSS rescore
  32. 2026-05-26 04:27 UTCEG score recompute
  33. 2026-05-26 04:27 UTCVendor advisory

Frequently asked(5)

What is CVE-2022-23221?
CVE-2022-23221 is a critical vulnerability published on January 19, 2022. H2 Console before 2.1.210 allows remote attackers to execute arbitrary code via a jdbc:h2:mem JDBC URL containing the IGNOREUNKNOWNSETTINGS=TRUE;FORBID_CREATION=FALSE;INIT=RUNSCRIPT substring, a different vulnerability than CVE-2021-42392.
When was CVE-2022-23221 disclosed?
CVE-2022-23221 was first published in the National Vulnerability Database on January 19, 2022, with the most recent update on May 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-23221 actively exploited?
CVE-2022-23221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-23221?
CVE-2022-23221 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-23221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-23221, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23221

Explore →

Is Your Infrastructure Affected by CVE-2022-23221?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs