dbt has an implicit override for built-in materializations from installed packages
Low4.2CVE-2024-40637 · Published Jul 17, 2024 · updated Sep 10, 2026
### Impact _What kind of vulnerability is it? Who is impacted?_ When a user installs a [package](https://docs.getdbt.com/docs/build/packages) in dbt, it has the ability to override macros, materializations, and other core components of dbt. This is by design, as it allows packages to extend and customize dbt's functionality. However, this also means that a malicious package could potentially override these components with harmful code. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Fixed on 1.8.0, and patched for 1.6.14 and 1.7.14 releases. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Previously, a materialization defined in a package that shared a name with one of the built-in materializations would be preferred by default, without user action which is surprising and makes it more difficult to detect the insecure behaviour. We've changed the default behaviour to require explicit overrides by users in `1.8.0`, and provided the ability to opt-out of built-in materialization overrides in 1.6 and 1.7 via the `flags.require_explicit_package_overrides_for_builtin_materializations: False` conf...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| dbt-core PyPI | >= 1.6.0, < 1.6.14 | 1.6.14 |
| >= 1.7.0, < 1.7.14 | 1.7.14 |
Details and references
### Impact _What kind of vulnerability is it? Who is impacted?_ When a user installs a [package](https://docs.getdbt.com/docs/build/packages) in dbt, it has the ability to override macros, materializations, and other core components of dbt. This is by design, as it allows packages to extend and customize dbt's functionality. However, this also means that a malicious package could potentially override these components with harmful code. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Fixed on 1.8.0, and patched for 1.6.14 and 1.7.14 releases. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Previously, a materialization defined in a package that shared a name with one of the built-in materializations would be preferred by default, without user action which is surprising and makes it more difficult to detect the insecure behaviour. We've changed the default behaviour to require explicit overrides by users in `1.8.0`, and provided the ability to opt-out of built-in materialization overrides in 1.6 and 1.7 via the `flags.require_explicit_package_overrides_for_builtin_materializations: False` configuration in `dbt_project.yml` Versions older than 1.6 are EOL. ### References _Are there any links users can visit to find out more?_ * dbt documentation: https://docs.getdbt.com/reference/global-configs/legacy-behaviors#behavior-change-flags * https://www.elementary-data.com/post/are-dbt-packages-secure-the-answer-lies-in-your-dwh-policies * https://www.equalexperts.com/blog/tech-focus/are-you-at-risk-from-this-critical-dbt-vulnerability/ * https://tempered.works/posts/2024/07/06/preventing-data-theft-with-gcp-service-controls/
- CVSS 3.1
- CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-74, CWE-89, CWE-913
- Also known as
- CVE-2024-40637, PYSEC-2024-66
- github.com/dbt-labs/dbt-core/security/advisories/GHSA-p3f3-5ccg-83xq
- nvd.nist.gov/vuln/detail/CVE-2024-40637
- github.com/dbt-labs/dbt-core/commit/3c82a0296d227cb1be295356df314c11716f4ff6
- github.com/dbt-labs/dbt-core/commit/87ac4deb00cc9fe334706e42a365903a1d581624
- docs.getdbt.com/docs/build/packages
- docs.getdbt.com/reference/global-configs/legacy-behaviors#behavior-change-flags
- github.com/dbt-labs/dbt-core
- github.com/pypa/advisory-database/tree/main/vulns/dbt-core/PYSEC-2024-66.yaml
- tempered.works/posts/2024/07/06/preventing-data-theft-with-gcp-service-controls
- www.elementary-data.com/post/are-dbt-packages-secure-the-answer-lies-in-your-dwh-policies
- www.equalexperts.com/blog/tech-focus/are-you-at-risk-from-this-critical-dbt-vulnerability
More dbt Core advisories
All dbt Core| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| May 282024 | dbt allows Binding to an Unrestricted IP Address via socketsocket | Medium5.3 | 1.6.15+2 more |
| Apr 222024 | dbt uses a SQLparse version with a high vulnerability | High7.5 | 1.6.13+1 more |
| Dec 82023 | dbt-core's secret env vars written to package-lock.json in plaintext | Low3.2 | 1.7.3 |