Metabase 0.58 · Version Status
Metabase 0.58 End of Life Date
Metabase 0.58 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚡
Metabase 0.58 reaches end of life on February 17, 2027. Plan your migration now — 164 days remaining.
📅 Get reminded before Metabase 0.58 reaches EOL on February 17, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Feb 17, 2027
164 days remaining
Latest Release
0.58.32.2
LTS release
Release Date
Dec 17, 2025
Metabase 0.58 series
Lifecycle detail
Metabase 0.58 was released on December 17, 2025 and support is scheduled to end on February 17, 2027 — a planned supported lifespan of 1 year and 2 months, longer than the 7 months median for Metabase releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 0.58.32.2, published September 4, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Metabase 0.58 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 0.9 |
0.9.3 |
Supported |
EOL |
| 0.10 |
0.10.4.1 |
Supported |
EOL |
| 0.11 |
0.11.3 |
Supported |
EOL |
| 0.12 |
0.12.1 |
Supported |
EOL |
| 0.13 |
0.13.3 |
Supported |
EOL |
| 0.14 |
0.14.1 |
Supported |
EOL |
| 0.15 |
0.15.1 |
Supported |
EOL |
| 0.16 |
0.16.1 |
Supported |
EOL |
What does Metabase 0.58 end of life mean?
When Metabase 0.58 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Metabase 0.58 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Metabase 0.58 reach end of life?
Metabase 0.58 reached end of life on February 17, 2027. That is 164 days remaining.
Is Metabase 0.58 still supported?
Metabase 0.58 is still supported but approaching end of life on February 17, 2027. Begin planning your migration now.
What should I upgrade to from Metabase 0.58?
What are the security risks of running Metabase 0.58 past EOL?
When Metabase 0.58 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Metabase should migrate immediately or implement compensating controls.