What is the CVSS score of CVE-2026-59826?

CVE-2026-59826 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.4%.

Which versions of Metabase are affected by CVE-2026-59826?

Metabase (open-source BI/analytics platform) versions 1.55.0 and later are vulnerable to remote code execution via improper H2 database validation, allowing authenticated administrators to achieve…. A patch is available.

How to fix or mitigate CVE-2026-59826?

Within 24 hours: audit all Metabase administrator accounts and disable unnecessary admin privileges; restrict network access to Metabase to trusted IP ranges only. Within 7 days: enable detailed logging of database connection attempts; implement network segmentation if Metabase has access to sensitive systems. Within 30 days: monitor vendor security advisories for patch release; coordinate with Metabase community and evaluate alternative BI platforms if patch delays extend beyond 60 days.

Metabase CVE-2026-59826

EUVD-2026-42664 CRITICAL

Code Injection (CWE-94)

2026-07-09 security-advisories@github.com

Code Injection Java RCE Metabase

9.1

CVSS 3.1 · Vendor: github

Severity by source

Vendor (github) PRIMARY

9.1 CRITICAL

AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

vuln.today AI

9.1 CRITICAL

Network-reachable admin endpoint (AV:N, PR:H because admin rights are required), no user interaction, and H2 code execution escapes the app to the host (S:C) with full C/I/A impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Jul 09, 2026 - 19:01 EUVD

Analysis Generated

Jul 09, 2026 - 18:42 vuln.today

DescriptionCVE.org

Metabase is an open-source business intelligence and embedded analytics tool. From 1.55.0 until 1.58.15.1, 1.59.12, 1.60.6.3, and 1.61.2, Metabase did not validate unsafe H2 connection properties on one database-creation code path, allowing an authenticated administrator to register a crafted H2 database connection and execute arbitrary Java code on the Metabase server. This issue is fixed in versions 1.58.15.1, 1.59.12, 1.60.6.3, and 1.61.2.

Articles & Coverage 2

News 3 New Java Vulnerabilities - 2 Critical, 1 High Severity Jul 10, 2026 News Critical RCE in Metabase via H2 JDBC Injection - CVE-2026-59826 Jul 09, 2026

AnalysisAI

Remote code execution in Metabase (open-source BI/analytics platform) versions 1.55.0 through the fixed releases arises because one database-creation code path failed to validate unsafe H2 JDBC connection properties, letting an authenticated administrator register a crafted H2 datasource and run arbitrary Java on the server host. Because the CVSS scope is Changed (S:C), successful exploitation escapes the application context and yields full host compromise. No public exploit has been identified at time of analysis and it is not listed in CISA KEV, but the CVSS base score of 9.1 and RCE nature make it a high-priority patch for any exposed Metabase instance.

Technical ContextAI

Metabase supports many database backends via JDBC, including the embedded H2 engine. H2's JDBC URL and connection properties can invoke Java features (for example INIT scripts, TRIGGER/ALIAS definitions calling arbitrary Java, or the FILE_READ/CREATE ALIAS mechanisms) that execute code inside the JVM running Metabase. The root cause is CWE-94 (Improper Control of Generation of Code / code injection): the normal database-add flow strips or rejects dangerous H2 properties, but one particular creation code path (from 1.55.0 onward) omitted that validation, so an admin-supplied H2 connection string could smuggle code-executing properties. The affected component is the Metabase server itself (both the open-source 0.x/1.x lines share the same codebase), and the exploit runs with the privileges of the Metabase JVM process.

RemediationAI

Vendor-released patch: upgrade to 1.58.15.1, 1.59.12, 1.60.6.3, or 1.61.2 (open-source tags v0.58.15.1, v0.59.12, v0.60.6.3, v0.61.2), choosing the fixed release on your current release line; the fix commit is 74032e5e0a5a70dc45a6a744d37b9ba24eee8d01 and full details are in advisory https://github.com/metabase/metabase/security/advisories/GHSA-8wx2-rxp2-4x35. If you cannot patch immediately, the most effective compensating controls are to tightly restrict who holds Metabase administrator privileges and to require strong MFA on admin accounts, since exploitation needs an admin session; additionally, avoid granting the ability to add or edit database connections beyond a minimal trusted set, and place the Metabase admin interface behind a VPN or IP allowlist so an attacker cannot reach the database-creation endpoint even with stolen low-value credentials. As a targeted hardening measure, prevent registration of H2-type databases where the feature is not needed and monitor for creation of H2 datasources with unusual connection properties; the trade-off is reduced administrative flexibility for teams that legitimately use embedded H2. Note these controls reduce but do not eliminate risk from a fully compromised admin account - patching is the durable fix.