RCE in H2 Console

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2021-42392: 83.18% estimated exploitation activity in the next 30 days; percentile 99.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact H2 Console in versions since 1.1.100 (2008-10-14) to 2.0.204 (2021-12-21) inclusive allows loading of custom classes from remote servers through JNDI. H2 Console doesn't accept remote connections by default. If remote access was enabled explicitly and some protection method (such as security constraint) wasn't set, an intruder can load own custom class and execute its code in a process with H2 Console (H2 Server process or a web server with H2 Console servlet). It is also possible to load them by creation a linked table in these versions, but it requires ADMIN privileges and user with ADMIN privileges has full access to the Java process by design. These privileges should never be granted to untrusted users. Patches Since version 2.0.206 H2 Console and linked tables explicitly forbid attempts to specify LDAP URLs for JNDI. Only local data sources can be used. Workarounds H2 Console should never be available to untrusted users. -webAllowOthers is a dangerous setting that should…

Published by the source

6 Jan 2022, 23:55 UTC

Last modified by the source

25 Feb 2023, 00:31 UTC

Source last checked

26 Oct 2026, 16:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h376-j262-vhq6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-42392

Advisory: RCE in H2 Console
IDs: CVE-2021-42392, GHSA-h376-j262-vhq6
Record: https://patchnext.com/advisories/cve-2021-42392 (revision 1, source checked 26 Oct 2026, 16:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.h2database:h2 2.0.206. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.h2database:h2: affected >= 1.1.100, < 2.0.206; fixed in 2.0.206

## Suggested inspection (read-only)
- Maven com.h2database:h2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.h2database:h2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h376-j262-vhq6 (GitHub-reviewed advisory GHSA-h376-j262-vhq6 lists affected ranges: Maven com.h2database:h2 >=1.1.100 <2.0.206)

Commands are suggestions: review each one before running it.