CVE-2026-59827
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 · uneditedMetabase is an open-source business intelligence and embedded analytics tool. Prior to 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4, Metabase instances with an H2 database connection, including the default sample database, deserialize arbitrary Java objects returned in H2 native query result columns of type OTHER without validation, allowing an authenticated user who can run native H2 queries to execute code on the Metabase server. This issue is fixed in versions 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4.
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 confidenceMetabase deserializes arbitrary Java objects from H2 database query results in columns of type OTHER without validation, allowing authenticated users with native H2 query permissions to achieve remote code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.58.0, < 0.58.15>= 0.59.0, < 0.59.12>= 0.60.0, < 0.60.6.3>= 0.61.0, < 0.61.1.4>= 1.58.0, < 1.58.15>= 1.59.0, < 1.59.12>= 1.60.0, < 1.60.6.3>= 1.61.0, < 1.61.1.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the installed Metabase versionCheck the Metabase admin panel (Settings > About) or examine the metabase.VERSION file in the installation directory, or run: java -jar metabase.jar versionAffected if The installed version falls within any of these ranges: >= 0.58.0 and < 0.58.15; >= 0.59.0 and < 0.59.12; >= 0.60.0 and < 0.60.6.3; >= 0.61.0 and < 0.61.1.4; >= 1.58.0 and < 1.58.15; >= 1.59.0 and < 1.59.12; >= 1.60.0 and < 1.60.6.3; >= 1.61.0 and < 1.61.1.4
-
Determine if H2 is used as the Metabase application databaseCheck the connection string in Metabase configuration (metabase.db.type and metabase.db.connection-uri in metabase.db in env settings, or the database connection settings file). Look for jdbc:h2: in the connection URL.Affected if The application database is H2 (jdbc:h2: or h2 in the database type setting)
-
Verify if native H2 query execution permissions are granted to any usersIn Metabase admin panel, go to Settings > Permissions > Data and check if any user groups have native query writing permissions (the Native icon under Permissions column) enabled for the H2 database. Alternatively, query the permissions table in the Metabase application database.Affected if Any user group has native query write permissions enabled for the H2 database
-
Check for columns of type OTHER in custom H2 queries or saved questionsReview any custom questions, native queries, or saved objects that execute H2 queries. Look for explicit type casting to OTHER (for example, RUNNING TOTAL or specific H2-specific type declarations). This may require auditing custom SQL/native queries in Metabase.Affected if Custom H2 queries or saved questions contain columns explicitly typed as OTHER (H2's ANY type)
A user is affected if they run a vulnerable Metabase version AND use H2 as the application database AND have native H2 query permissions enabled for any user, creating a path for deserialization attacks.
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 · scoped0.58.150.59.120.60.6.3
Upgrade Metabase to version 1.58.15, 1.59.12, 1.60.6.3, or 1.61.1.4. As a compensating control, restrict or disable native H2 query execution permissions until the upgrade is applied.
Upgrade to 1.61.1.4 (or the latest 1.61.x stable release); alternatively, for older branches: 1.60.6.3, 1.59.12, or 1.58.15
- Backup your Metabase data and configuration before proceeding
- Stop the Metabase instance
- For installations using JAR files: replace the existing Metabase JAR with the new version
- For Docker deployments: update the image tag to the fixed version
- Restart Metabase and verify the application starts successfully
- Test that native query functionality works correctly
- Review the release notes for your chosen version for any additional configuration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59827 — 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-59827 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