Security readout for executives and security teams
Plain-English summary
A vulnerable Metabase server can be made to run arbitrary Java code if an authenticated administrator adds a specially crafted H2 database connection. This is critical because successful abuse affects the Metabase server itself, not just dashboard data. Fixed versions are available.
Executive priority
Treat this as urgent for any production Metabase instance. Although exploitation requires admin privileges, a successful attack can compromise the underlying server, so vulnerable systems should be upgraded promptly and admin access reviewed.
Technical view
Metabase versions 1.55.0 through the listed vulnerable branch ranges failed to validate unsafe H2 connection properties on one database-creation path. The flaw is CWE-94 code injection with CVSS 9.1, requiring high privileges but allowing network-reachable arbitrary Java code execution with changed scope.
Likely exposure
Exposure is limited to Metabase deployments running affected versions where an authenticated administrator can create database connections. Internet-facing admin panels or compromised admin accounts raise urgency.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. The attack requires administrator privileges, but the impact is severe because it can execute code on the Metabase server.
Researcher notes
The key research boundary is the vulnerable database-creation path and H2 connection property validation. Sources identify fixed versions and a remediation commit, but do not provide evidence of exploitation in the wild.
Mitigation direction
- Upgrade to 1.58.15.1, 1.59.12, 1.60.6.3, 1.61.2, or later fixed versions.
- Prioritize externally reachable or shared Metabase instances first.
- Restrict Metabase administrator access to trusted users only.
- Review vendor advisory and release notes for branch-specific upgrade guidance.
- Monitor for unexpected Metabase database connection changes.
Validation and detection
- Inventory all Metabase instances and record exact versions.
- Compare versions against the affected branch ranges in the CVE record.
- Confirm upgraded instances report a fixed version.
- Review configured database connections for unexpected H2 entries.
- Check administrative change history where available for unusual database creation events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-59826 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/metabase/metabase/security/advisories/GHSA-8wx2-rxp2-4x35CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/metabase/metabase/commit/74032e5e0a5a70dc45a6a744d37b9ba24eee8d01CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/metabase/metabase/releases/tag/v0.58.15.1CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/metabase/metabase/releases/tag/v0.59.12CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/metabase/metabase/releases/tag/v0.60.6.3CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/metabase/metabase/releases/tag/v0.61.2CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.