MetalLB 0.15 · Version Status
MetalLB 0.15 End of Life Date
MetalLB 0.15 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.
⚠
MetalLB 0.15 is past end of life. This version no longer receives security patches. 113 days past EOL — migrate to a supported version immediately.
EOL Date
May 20, 2026
113 days past EOL
Latest Release
0.15.3
Standard release
Release Date
Jun 3, 2025
MetalLB 0.15 series
Lifecycle detail
MetalLB 0.15 was released on June 3, 2025 and support ended on May 20, 2026 — a supported lifespan of 1 year, shorter than the 1 year and 4 months median for MetalLB releases. The last patch it will ever receive is 0.15.3, published December 4, 2025 — 6 months before support ended. It has been without security patches for 4 months.
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 MetalLB 0.15 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 0.13 |
0.13.12 |
Jan 29, 2024 |
EOL |
| 0.14 |
0.14.9 |
Jun 3, 2025 |
EOL |
| → 0.15 |
0.15.3 |
May 20, 2026 |
EOL |
| 0.16 |
0.16.1 |
EOL |
Active |
What does MetalLB 0.15 end of life mean?
When MetalLB 0.15 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 MetalLB 0.15 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to MetalLB 0.16 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does MetalLB 0.15 reach end of life?
MetalLB 0.15 reached end of life on May 20, 2026. This version is no longer receiving security patches.
Is MetalLB 0.15 still supported?
No. MetalLB 0.15 reached end of life on May 20, 2026 and is no longer receiving security patches.
What should I upgrade to from MetalLB 0.15?
The recommended upgrade from MetalLB 0.15 is
MetalLB 0.16 — the latest actively supported version. Check the
MetalLB full timeline for all supported versions.
What are the security risks of running MetalLB 0.15 past EOL?
When MetalLB 0.15 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 MetalLB should migrate immediately or implement compensating controls.