CVE-2026-41042
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Gravitino's testConnection API allows unauthenticated callers to provide a malicious H2 JDBC URL containing the H2 INIT parameter, which enables arbitrary Java code execution on the server. This occurs because the API does not validate or sanitize the JDBC connection string before passing it to the H2 driver, allowing attackers to inject malicious INIT scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gravitino versionCheck the installed Apache Gravitino version by reviewing the build metadata, WAR/JAR file name, or the version reported by the Gravitino server startup logs. Compare against the affected versions (those prior to the 1.2.1 fix).Affected if The installed Gravitino version is older than 1.2.1 and the testConnection API is reachable.
-
Verify testConnection API exposureExamine network access controls (firewall rules, API gateway policies, or reverse proxy configuration) to determine if the /api、金属.../testConnection endpoint (or similar path under which this API is served) is exposed to untrusted networks or unauthenticated users.Affected if The testConnection API is accessible without authentication from untrusted networks.
-
Confirm H2 database usageReview Gravitino's database configuration files or environment variables to determine if H2 is configured as the metadata store. Look for JDBC connection strings using the h2: protocol in the configuration.Affected if H2 is configured as the database backend and is reachable via the testConnection API.
A user is affected if they run a Gravitino version prior to 1.2.1 with the testConnection API exposed to untrusted callers while H2 is in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Apache Gravitino to version 1.2.1 or later. If immediate upgrade is not possible, restrict network access to the testConnection API and consider disabling H2 usage in production environments.
1.2.1
- Download Apache Gravitino version 1.2.1 from the official Apache releases
- Stop the current Gravitino service
- Replace the existing Gravitino installation with version 1.2.1
- Restart the Gravitino service
- Verify the upgrade by checking the Gravitino version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41042 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data