https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T22:40:40.554827+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2024-40637 CVE-2024-40637 — Implicit override for built-in materializations from installed packages in dbt-core 2026-10-03T22:40:40.556812+00:00

Affected: dbt-labs dbt-core

dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. When a user installs a package 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. This issue has been fixed in versions 1.8.0, 1.6.14 and 1.7.14. Users are advised to upgrade. There are no kn own workarounds for this vulnerability. Users updating to either 1.6.14 or 1.7.14 will need to set `flags.require_explicit_package_overrides_for_builtin_materializations: False` in their configuration in `dbt_project.yml`.

 https://cve.radiocsirt.org/vuln/ghsa-p3f3-5ccg-83xq GHSA-p3f3-5ccg-83xq — dbt has an implicit override for built-in materializations from installed packages 2026-10-03T22:40:40.556874+00:00

Affected: PyPI: dbt-core

### 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-packag…