dbt Core 1.7 · Version Status
dbt Core 1.7 End of Life Date
dbt Core 1.7 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
dbt Core 1.7 is past end of life. This version no longer receives security patches. 646 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 2, 2024
646 days past EOL
Latest Release
1.7.19
Standard release
Release Date
Nov 2, 2023
dbt Core 1.7 series
Lifecycle detail
dbt Core 1.7 was released on November 2, 2023 and support ended on November 2, 2024 — a supported lifespan of 1 year, in line with the 1 year median for dbt Core releases. The last patch it will ever receive is 1.7.19, published December 2, 2024 — 30 days after the published end-of-life date. It has been without security patches for 1 year and 9 months. 4 newer dbt Core releases have shipped since.
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 dbt Core 1.7 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.9 |
Dec 3, 2022 |
EOL |
| 1.1 |
1.1.5 |
Apr 28, 2023 |
EOL |
| 1.2 |
1.2.6 |
Jul 26, 2023 |
EOL |
| 1.3 |
1.3.7 |
Oct 12, 2023 |
EOL |
| 1.4 |
1.4.9 |
Jan 25, 2024 |
EOL |
| 1.5 |
1.5.11 |
Apr 27, 2024 |
EOL |
| 1.6 |
1.6.18 |
Jul 30, 2024 |
EOL |
| → 1.7 |
1.7.19 |
Nov 2, 2024 |
EOL |
What does dbt Core 1.7 end of life mean?
When dbt Core 1.7 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 1.7 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to dbt Core 1.12 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does dbt Core 1.7 reach end of life?
dbt Core 1.7 reached end of life on November 2, 2024. This version is no longer receiving security patches.
Is dbt Core 1.7 still supported?
No. dbt Core 1.7 reached end of life on November 2, 2024 and is no longer receiving security patches.
What should I upgrade to from dbt Core 1.7?
The recommended upgrade from dbt Core 1.7 is
dbt Core 1.12 — the latest actively supported version. Check the
dbt Core full timeline for all supported versions.
What are the security risks of running dbt Core 1.7 past EOL?
When dbt Core 1.7 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.