Advisory record · GHSA-h376-j262-vhq6

RCE in H2 Console

CVSS 9.8 CriticalCriticalEPSS 0.83 · 99th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.83 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 6 Jan 2022, 23:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.h2database:h2Maven>=1.1.100, <2.0.2062.0.206
Identifiers
GHSA-h376-j262-vhq6 · CVE-2021-42392
Weakness (CWE)
CWE-502
Published
6 Jan 2022
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-h376-j262-vhq6 affects the H2 Console in the Maven package com.h2database:h2, versions 1.1.100 up to 2.0.206 (excluding 2.0.206). The source describes the flaw as allowing custom classes to be loaded from remote servers through JNDI when remote access was enabled and no protection such as a security constraint was set, letting an intruder run code in the process hosting the console. Upgrade to version 2.0.206, which forbids LDAP URLs for JNDI; also keep the console away from untrusted users and avoid the -webAllowOthers setting.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.83, the 99th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.