dbt has an implicit override for built-in materializations from installed packages
Published Jul 16, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
dbt has an implicit override for built-in materializations from installed packages
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
_What kind of vulnerability is it? Who is impacted?_
Potential impact
What kind of vulnerability is it? Who is impacted? 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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- docs.getdbt.com ↗
- docs.getdbt.com ↗
- Patch commit ↗
- Patch commit ↗
- Security advisory ↗
- tempered.works ↗
- www.elementary-data.com ↗
- www.equalexperts.com ↗
Record history
Published Jul 16, 2024 · Last refreshed Nov 3, 2026