Cpe:2.3:a:metabase:metabase:*:*:*:*:-:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3ametabasemetabase-/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 26 Aug 2026 09:03:48 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgCritical Pre-Authentication RCE in Metabase (CVE-2023-38646)https://feed.craftedsignal.io/briefs/2026-08-metabase-rce/Wed, 26 Aug 2026 09:03:48 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-metabase-rce/A critical pre-authentication Remote Code Execution vulnerability in Metabase allows unauthenticated attackers to execute arbitrary system commands via malicious H2 database connection strings.CVE-2023-38646 is a critical vulnerability affecting multiple versions of Metabase (prior to 0.43.7.2, 1.43.7.2, 0.44.7.1, 1.44.7.1, 0.45.4.1, 1.45.4.1, 0.46.6.1, and 1.46.6.1). This vulnerability exists within the setup validation process, specifically in the /api/setup/validate endpoint. An unauthenticated attacker can supply a specially crafted JSON payload that includes a malicious H2 database connection string. Due to improper input validation and handling of the subname parameter, the application is forced to execute system-level commands through the H2 database engine's driver functionality. The recent publication of multiple functional proof-of-concept exploits significantly lowers the barrier for exploitation, making immediate remediation essential for any internet-exposed Metabase instance.

Attack Chain

  1. Attacker identifies an internet-facing Metabase server.
  2. Attacker sends a crafted POST request to the /api/setup/validate endpoint.
  3. The request includes a JSON body with a details object containing a malicious subname parameter.
  4. The subname parameter is configured to use the org.h2.Driver class with a path containing a malicious SQL CREATE TRIGGER statement.
  5. The Metabase application processes the payload, triggering the H2 database driver to initialize the malicious connection string.
  6. The CREATE TRIGGER statement executes on the backend, invoking Java's Runtime.getRuntime().exec() method.
  7. The attacker-specified shell command (e.g., base64 encoded bash command) executes on the underlying operating system.
  8. Successful execution leads to full application or host compromise, potentially allowing for persistent access or further exfiltration.

Impact

Successful exploitation of CVE-2023-38646 grants an attacker full remote code execution privileges with the context of the Metabase application. This exposes the organization to complete data exfiltration, service disruption, and potential lateral movement into the internal network where the database instance is hosted. With a CVSS score of 9.8, the impact includes full loss of confidentiality, integrity, and availability.

Recommendation

  • Immediately upgrade Metabase to the latest patched version (>= 0.43.7.2, 1.43.7.2, 0.44.7.1, 1.44.7.1, 0.45.4.1, 1.45.4.1, 0.46.6.1, or 1.46.6.1).
  • Monitor webserver logs for unauthorized POST requests to /api/setup/validate containing strings indicative of H2 driver initialization or SQL trigger keywords (e.g., CREATE TRIGGER, org.h2.Driver, RUNSCRIPT).
  • Restrict network access to the Metabase management interface, ensuring it is not accessible from the public internet.
  • Deploy the provided Sigma rule to detect exploitation attempts at the webserver level.
]]>criticaladvisory