Unauthenticated H2 JDBC URL Code Execution in Apache Gravitino

Unauthenticated callers can supply a malicious H2 JDBC URL through the testConnection API, which executes arbitrary Java code on the server via H2's INIT parameter. Vulnerability in Apache Gravitino. This issue affects Apache Gravitino: before 1.2.1. Users are recommended to upgrade to version 1.2.1, which fixes the issue. This issue only happens when using H2, and H2 is mainly used for testing and local development. Also, Gravitino is typically deployed in the internal environment, so the severity is low.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Apache Gravitino versions before 1.2.1 contain a critical vulnerability allowing unauthenticated attackers to execute arbitrary Java code through the testConnection API. By supplying a malicious H2 JDBC URL with an INIT parameter, attackers can bypass authentication and achieve remote code execution on the server. While H2 is primarily used for testing and local development, and Gravitino typically runs in internal environments, the CVSS 9.1 score reflects the severity of unauthenticated RCE. Any organization running Gravitino 1.2.0 or earlier with H2 database connectivity exposed—even in development or staging—faces critical risk from this input validation flaw (CWE-20).

Casky's 322 mapped skills enable detection of this vulnerability through analysis of MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify attack patterns including: suspicious testConnection API calls with H2 JDBC URLs containing INIT parameters, unauthenticated requests to database configuration endpoints, and Java process execution anomalies following connection attempts. Claude AI's extended reasoning capability correlates these signals across input validation gaps, suspicious parameter handling, and post-exploitation behavior, surfacing the specific chain of attack—malicious URL → unsafe parameter parsing → code execution. Security teams would receive findings highlighting the exact API endpoint vulnerability, H2-specific exploitation vectors, and recommendations to upgrade to version 1.2.1 immediately.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-41042.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-41042

Casky has 322 skills that investigate the attack patterns behind CVE-2026-41042. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn