Metabase 0.63 · Version Status
Metabase 0.63 End of Life Date
Metabase 0.63 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.63 reaches end of life on November 1, 2026. Plan your migration now — 56 days remaining.
📅 Get reminded before Metabase 0.63 reaches EOL on November 1, 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 1, 2026
56 days remaining
Latest Release
0.63.16.6
Standard release
Release Date
Jul 7, 2026
Metabase 0.63 series
Lifecycle detail
Metabase 0.63 was released on July 7, 2026 and support is scheduled to end on November 1, 2026 — a planned supported lifespan of 4 months, shorter than the 7 months median for Metabase releases. It is not an LTS release; Metabase reserves longer patch windows for its LTS versions. Its most recent patch is 0.63.16.6, 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.63 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.63 end of life mean?
When Metabase 0.63 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.63 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.63 reach end of life?
Metabase 0.63 reached end of life on November 1, 2026. That is 56 days remaining.
Is Metabase 0.63 still supported?
Metabase 0.63 is still supported but approaching end of life on November 1, 2026. Begin planning your migration now.
What should I upgrade to from Metabase 0.63?
What are the security risks of running Metabase 0.63 past EOL?
When Metabase 0.63 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.