Complete end-of-life dates, support windows, and security status for all Bazel versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4 LTS | 4.2.4 | Jan 21, 2021 | Jan 31, 2024 | 829 days past EOL | EOL |
| 5 LTS | 5.4.1 | Jan 19, 2022 | Jan 31, 2025 | 463 days past EOL | EOL |
| 6 LTS | 6.6.0 | Dec 19, 2022 | Dec 31, 2025 | 129 days past EOL | EOL |
| 7 LTS | 7.7.1 | Dec 11, 2023 | Dec 31, 2026 | 236 days remaining | Active |
| 8 LTS | 8.7.0 | Dec 9, 2024 | Dec 31, 2027 | 601 days remaining | Active |
| 9 LTS | 9.1.0 | Jan 20, 2026 | Dec 31, 2028 | 967 days remaining | Active |
When a Bazel version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Bazel should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →