LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22805: Metabase channel test endpoint can reach internal local addresses

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.

LowCVSS 2.1Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-22805 is a low-severity Metabase issue where a channel test endpoint could reach internal local addresses. The business risk is mainly for self-hosted Metabase deployments located near other unsecured internal resources and allowing users to create subscriptions.

Executive priority

Treat as routine patching unless Metabase is self-hosted beside sensitive internal services and many users can create subscriptions. Prioritize upgrade during the next maintenance cycle, faster for poorly segmented environments.

Technical view

Metabase before 55.13, 56.3, and 57.1 is affected by a CWE-918 server-side request forgery condition involving the channel test endpoint. The CVSS 4.0 score is 2.1, with network attack vector, high complexity, high privileges, and required attack conditions.

Likely exposure

Exposure appears limited to self-hosted Metabase instances on affected versions where users can create subscriptions and Metabase is colocated with unsecured internal resources. Hosted or differently isolated deployments are not identified as affected in the provided sources.

Exploitation context

The source bundle does not report active exploitation, and this CVE is not marked KEV. Exploitation requires high privileges and specific environmental conditions, reducing broad practical risk.

Researcher notes

Evidence is concise and vendor-centered. The advisory confirms affected versions and fixed releases but provides limited public detail on reachable targets or exploitation mechanics. Do not assume broader product impact beyond Metabase versions listed.

Mitigation direction

  • Upgrade Metabase to 55.13, 56.3, 57.1, or later as applicable.
  • Review the GitHub advisory for branch-specific upgrade guidance.
  • Restrict subscription creation to trusted users where operationally possible.
  • Avoid colocating Metabase with unsecured internal services.

Validation and detection

  • Identify all self-hosted Metabase instances and record their versions.
  • Confirm whether instances are below 55.13, 56.3, or 57.1.
  • Check whether users can create subscriptions in affected deployments.
  • Review internal network placement near unsecured local resources.
  • Confirm remediation by verifying the upgraded Metabase version.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookup
cve · low confidence lookup

CVE-2026-22805 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.1 (4.0)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
2.1CVSS 4.0LowCVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

2.1Low
CVSS 4.0 vector shape for CVE-2026-22805Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
metabasemetabase>= 0.57.0-beta, < 57.1, >= 0.56.0-beta, < 56.3, < 55.13Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.