dbcve.org
MetabaseApplication

CVE-2026-22805

HIGH · 8.6 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 0.55.13 / 0.56.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Metabase is an open-source data analytics platform. Prior to 55.13, 56.3, and 57.1, self-hosted Metabase instances that allow users to create subscriptions could be potentially impacted if their Metabase is colocated with other unsecured resources. This vulnerability is fixed in 55.13, 56.3, and 57.1.

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 · moderate confidence

Metabase versions prior to 55.13, 56.3, and 57.1 contain a vulnerability in the subscription creation functionality. When self-hosted Metabase instances are colocated with other unsecured resources, users with subscription creation privileges could potentially access or interact with those unsecured resources in unintended ways, likely through server-side request manipulation.

MitigationUpgrade self-hosted Metabase instances to version 55.13, 56.3, or 57.1. Additionally, ensure Metabase is deployed in isolation from unsecured internal resources and implement network segmentation between Metabase and sensitive internal services.

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
MetabaseApplication
Affected:< 0.55.13< 1.55.13>= 0.56.0, < 0.56.3>= 1.56.0, < 1.56.3= 0.57.0= 1.57.0

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Metabase deployment type
    Determine if this is a self-hosted instance (on-prem, docker, VM) versus Metabase Cloud. Check the login page branding or admin settings for 'Hosted on' information.
    Affected if Only self-hosted deployments are affected; Metabase Cloud instances are not vulnerable.
  2. Determine installed Metabase version
    Check the version in one of these ways: (1) Admin > Settings > About section shows the version number; (2) Query the /api/health endpoint which returns version info; (3) Inspect the JAR filename or Docker image tag used for deployment.
    Affected if Versions prior to 0.55.13 or 1.55.13, versions 0.56.0-0.56.2 or 1.56.0-1.56.2, and versions 0.57.0 or 1.57.0 are affected.
  3. Check if subscription feature is accessible
    Verify if users have access to the subscriptions/dashboards feature. Look for 'Subscriptions' or 'Alert' options in the UI navigation, typically under a bell icon or in dashboard menus.
    Affected if The vulnerability requires subscription creation privileges; if no user can create subscriptions, the attack surface is reduced.
  4. Assess network colocation
    Review network architecture to determine if the Metabase server shares a network or subnet with unsecured internal resources (internal APIs, databases, admin panels, development services) without network segmentation or firewall rules.
    Affected if If Metabase is deployed on the same network segment as unsecured internal resources without isolation, the SSRF-like exploitation path exists.

A self-hosted Metabase instance running an affected version (pre-55.13, 56.0-56.2, or 57.0) with subscription feature enabled and network access to unsecured internal resources is vulnerable to this issue.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.55.13 / 0.56.3 / 1.55.13 or later
Fixed in 0.55.130.56.31.55.13
Interim mitigation

Upgrade self-hosted Metabase instances to version 55.13, 56.3, or 57.1. Additionally, ensure Metabase is deployed in isolation from unsecured internal resources and implement network segmentation between Metabase and sensitive internal services.

Recommended fix High confidence

Upgrade to version 0.55.13, 0.56.3, 1.55.13, 1.56.3, or preferably 57.1 or later

  1. 1. Identify the current Metabase version by checking the Metabase admin panel or the jar file name
  2. 2. If running version 0.55.x or earlier: upgrade to version 0.55.13
  3. 3. If running version 0.56.x: upgrade to version 0.56.3
  4. 4. If running version 1.55.x: upgrade to version 1.55.13
  5. 5. If running version 1.56.x: upgrade to version 1.56.3
  6. 6. Alternatively, upgrade to the latest stable version 57.1 or later which contains all fixes
  7. 7. After upgrade, verify the Metabase instance is running correctly and review audit logs for any suspicious subscription creation activity that may indicate exploitation attempts
Caveat Review release notes for breaking changes between your current version and target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metabase Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22805 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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