Complete end-of-life dates, support windows, and security status for all Backdrop versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.27 | 1.27.3 | Jan 15, 2024 | Sep 15, 2024 | 601 days past EOL | EOL |
| 1.28 | 1.28.5 | May 15, 2024 | Jan 15, 2025 | 479 days past EOL | EOL |
| 1.29 | 1.29.5 | Sep 15, 2024 | May 15, 2025 | 359 days past EOL | EOL |
| 1.30 | 1.30.3 | Jan 15, 2025 | Sep 16, 2025 | 235 days past EOL | EOL |
| 1.31 | 1.31.2 | May 15, 2025 | Jan 16, 2026 | 113 days past EOL | EOL |
| 1.32 | 1.32.3 | Sep 16, 2025 | Already EOL | Supported | Active |
| 1.33 | 1.33.2 | Jan 16, 2026 | Already EOL | Supported | Active |
When a Backdrop 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 Backdrop 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 →