Metabase 0.65 · Version Status
Metabase 0.65 End of Life Date
Metabase 0.65 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.65 reaches end of life on January 1, 2027. Plan your migration now — 61 days remaining.
📅 Get reminded before Metabase 0.65 reaches EOL on January 1, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 1, 2027
61 days remaining
Latest Release
0.65.2.5
Standard release
Release Date
Oct 12, 2026
Metabase 0.65 series
Where these dates come from
End of lifeJan 1, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 12, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Metabase 0.65 was released on October 12, 2026 and support is scheduled to end on January 1, 2027 — a planned supported lifespan of 3 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.65.2.5, published October 31, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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.65 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. 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.65 end of life mean?
When Metabase 0.65 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Metabase 0.65 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Metabase 0.64 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Metabase 0.65 reach end of life?
Metabase 0.65 reaches end of life on January 1, 2027. That is 61 days remaining.
Is Metabase 0.65 still supported?
Metabase 0.65 is still supported but approaching end of life on January 1, 2027. Begin planning your migration now.
What should I upgrade to from Metabase 0.65?
The recommended upgrade from Metabase 0.65 is
Metabase 0.64 — the latest actively supported version. Check the
Metabase full timeline for all supported versions.
What are the security risks of running Metabase 0.65 past EOL?
When Metabase 0.65 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Metabase should migrate immediately or implement compensating controls.