Dbt Core 1.11 · Version Status

Dbt Core 1.11 End of Life Date

Dbt Core 1.11 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Dbt Core 1.11 is actively supported. EOL date: December 19, 2026.
EOL Date
Dec 19, 2026
224 days remaining
Latest Release
1.11.9
Standard release
Release Date
Dec 19, 2025
Dbt Core 1.11 series
← Dbt Core 1.10 All Dbt Core versions
All Dbt Core Versions
VersionLatestEOL DateStatus
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.11 end of life mean?

When Dbt Core 1.11 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.11 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Dbt Core 1.11 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Dbt Core 1.11 reach end of life?
Dbt Core 1.11 reached end of life on December 19, 2026. That is 224 days remaining.
Is Dbt Core 1.11 still supported?
Yes, Dbt Core 1.11 is currently supported. The EOL date is December 19, 2026.
What should I upgrade to from Dbt Core 1.11?
The recommended upgrade from Dbt Core 1.11 is Dbt Core 1.11 — 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.11 past EOL?
When Dbt Core 1.11 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.
Data from endoflife.date API · Generated at build time · How we source data →