dbt Core 2.0 · Version Status
dbt Core 2.0 End of Life Date
dbt Core 2.0 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.
✓
dbt Core 2.0 is actively supported. EOL date: September 14, 2027.
📅 Get reminded before dbt Core 2.0 reaches EOL on September 14, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Sep 14, 2027
359 days remaining
Latest Release
2.0.5
Standard release
Release Date
Sep 14, 2026
dbt Core 2.0 series
Lifecycle detail
dbt Core 2.0 was released on September 14, 2026 and support is scheduled to end on September 14, 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for dbt Core releases. Its most recent patch is 2.0.5, published September 18, 2026.
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 →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.9 |
Dec 3, 2022 |
EOL |
| 1.1 |
1.1.6 |
Apr 28, 2023 |
EOL |
| 1.2 |
1.2.7 |
Jul 26, 2023 |
EOL |
| 1.3 |
1.3.8 |
Oct 12, 2023 |
EOL |
| 1.4 |
1.4.10 |
Jan 25, 2024 |
EOL |
| 1.5 |
1.5.12 |
Apr 27, 2024 |
EOL |
| 1.6 |
1.6.19 |
Jul 30, 2024 |
EOL |
| 1.7 |
1.7.20 |
Nov 2, 2024 |
EOL |
What does dbt Core 2.0 end of life mean?
When dbt Core 2.0 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 dbt Core 2.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to dbt Core 2.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does dbt Core 2.0 reach end of life?
dbt Core 2.0 reached end of life on September 14, 2027. That is 359 days remaining.
Is dbt Core 2.0 still supported?
Yes, dbt Core 2.0 is currently supported. The EOL date is September 14, 2027.
What should I upgrade to from dbt Core 2.0?
The recommended upgrade from dbt Core 2.0 is
dbt Core 2.0 — the latest actively supported version. Check the
dbt Core full timeline for all supported versions.
What are the security risks of running dbt Core 2.0 past EOL?
When dbt Core 2.0 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 dbt Core should migrate immediately or implement compensating controls.