Complete end-of-life dates, support windows, and security status for all Dbt Core versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.9 | Dec 3, 2021 | Dec 3, 2022 | 1253 days past EOL | EOL |
| 1.1 | 1.1.5 | Apr 28, 2022 | Apr 28, 2023 | 1107 days past EOL | EOL |
| 1.2 | 1.2.6 | Jul 26, 2022 | Jul 26, 2023 | 1018 days past EOL | EOL |
| 1.3 | 1.3.7 | Oct 11, 2022 | Oct 12, 2023 | 940 days past EOL | EOL |
| 1.4 | 1.4.9 | Jan 25, 2023 | Jan 25, 2024 | 835 days past EOL | EOL |
| 1.5 | 1.5.11 | Apr 27, 2023 | Apr 27, 2024 | 742 days past EOL | EOL |
| 1.6 | 1.6.18 | Jul 31, 2023 | Jul 30, 2024 | 648 days past EOL | EOL |
| 1.7 | 1.7.19 | Nov 2, 2023 | Nov 2, 2024 | 553 days past EOL | EOL |
| 1.8 | 1.8.9 | May 9, 2024 | May 9, 2025 | 365 days past EOL | EOL |
| 1.9 | 1.9.10 | Dec 9, 2024 | Dec 9, 2025 | 151 days past EOL | EOL |
| 1.10 | 1.10.20 | Jun 16, 2025 | Jun 16, 2026 | 38 days remaining | Warning |
| 1.11 | 1.11.9 | Dec 19, 2025 | Dec 19, 2026 | 224 days remaining | Active |
When a Dbt Core 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 Dbt Core 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 →