CVE-2023-38646 in the critical feed json
Metabase open source before 0.46.6.1 and Metabase Enterprise before 1.46.6.1 allow attackers to execute arbitrary commands on the server, a…
published 2023-07-21 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-42445
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 99.5%
- EPSS 99.5% chance of exploitation in 30 days, percentile 99.9%
- public exploits
- 1
- Metasploit, plus a Nuclei check
Summary
Metabase open source before 0.46.6.1 and Metabase Enterprise before 1.46.6.1 allow attackers to execute arbitrary commands on the server, at the server's privilege level. Authentication is not required for exploitation. The other fixed versions are 0.45.4.1, 1.45.4.1, 0.44.7.1, 1.44.7.1, 0.43.7.2, and 1.43.7.2.
Patch / fix
- metabase metabase 0.43.7.2, 0.44.7.1, 0.45.4.1, 0.46.6.1, 1.43.7.2, 1.44.7.1, 1.45.4.1, 1.46.6.1
Timeline
- Published
- First public exploit (Metasploit exploit/linux/http/metabase_setup_token_rce)
Exploit prediction
99.48% chance of exploitation in the next 30 days, higher than 99.9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/linux/http/metabase_setup_token_rce Metabase Setup Token RCE metasploit exploit, excellent rank, 2023-07-22
- Nuclei template Metabase < 0.46.6.1 - Remote Code Execution nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
References
-
metabase.com
/blog/security-advisory
vendor-advisory
-
github.com
/metabase/metabase/releases/tag/v0.46.6.1
release-notes
-
news.ycombinator.com
/item?id=36812256
issue-tracking
-
github.com
/metabase/metabase/issues/32552
issue-tracking
- packetstormsecurity.com /files/174091/Metabase-Remote-Code-Execution.html
- packetstormsecurity.com /files/177138/Metabase-0.46.6-Remote-Code-Execution.html
Sources
- CVE List CVE-2023-38646
- NVD CVE-2023-38646
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.