CVE-2024-40637

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-07-17) is not newer than that change (2026-10-30), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-0033 (ENISA EUVD) · GHSA-p3f3-5ccg-83xq (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2024

Last Modified

October 30, 2026

Advisory Details (8)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit, github.
Web page

About behavior changes | dbt Developer Hub

https://docs.getdbt.com/reference/global-configs/legacy-behaviors#behavior-change-flags
Web page

Packages | dbt Developer Hub

https://docs.getdbt.com/docs/build/packages
Web page

Are you at risk from this critical dbt vulnerability? | Equal Experts

https://www.equalexperts.com/blog/tech-focus/are-you-at-risk-from-this-critical-dbt-vulnerability
Web page

Are dbt packages secure? The answer lies in your DWH policies | Elementary Data

https://www.elementary-data.com/post/are-dbt-packages-secure-the-answer-lies-in-your-dwh-policies
Web page

Preventing data theft with GCP service controls - Tempered Works Ltd.

https://tempered.works/posts/2024/07/06/preventing-data-theft-with-gcp-service-controls
GitHub advisoryMentions a patch (unverified)

Implicit override for built-in materializations from installed packages · Advisory · dbt-labs/dbt · GitHub

https://github.com/dbt-labs/dbt-core/security/advisories/GHSA-p3f3-5ccg-83xq
GitHub commit

commit 87ac4deb00cc (dbt-labs/dbt-core)

Fix landed in dbt-labs/dbt-core commit 87ac4deb00cc — awaiting tagged release

https://github.com/dbt-labs/dbt-core/commit/87ac4deb00cc9fe334706e42a365903a1d581624
GitHub commit

commit 3c82a0296d22 (dbt-labs/dbt-core)

Fix landed in dbt-labs/dbt-core commit 3c82a0296d22 — awaiting tagged release

https://github.com/dbt-labs/dbt-core/commit/3c82a0296d227cb1be295356df314c11716f4ff6

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdbt-core @ 1.6.14 (fixes >= 1.6.0, < 1.6.14)—ghsa
pipdbt-core @ 1.7.14 (fixes >= 1.7.0, < 1.7.14)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
dbt-core0.13.0 ... 1.7.9 (234 versions)
  • 1.6.0 up to 1.6.14: fixed in 1.6.14
  • 1.7.0 up to 1.7.14: fixed in 1.7.14
  • every version up to 1.6.14: fixed in 1.6.14
—

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 210 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-01 08:13 UTCGHSA enrichmentGHSA-p3f3-5ccg-83xq · GitHub severity LOW · GitHub CVSS 4.2
  4. 2026-11-01 08:13 UTCEG score recompute
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-30 14:48 UTCEG score recompute▲ 3.10
  8. 2026-10-30 14:46 UTCNVD updateCVSS v3 → 7.3 · severity → HIGH
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-25 17:05 UTCEG score recompute
  14. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-24 05:37 UTCEG score recompute
  17. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-10-18 07:08 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 71 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-12 17:49 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-11 21:14 UTCEG score recompute
  7. 2026-10-11 16:06 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-10 13:33 UTCOSV refresh
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-09-30 19:49 UTCEG score recompute
  20. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  26. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  29. 2026-09-20 22:57 UTCOSV refresh
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  31. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  32. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  33. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  34. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  35. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  36. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  37. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  38. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  39. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  40. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  41. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  42. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  43. 2026-09-05 15:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  44. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  45. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  46. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  47. 2026-09-01 22:27 UTCOSV refresh
  48. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  49. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  50. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  51. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  52. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  53. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  54. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  55. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  56. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  57. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  59. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  60. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  61. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  62. 2026-08-16 00:37 UTCOSV refresh
  63. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  64. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  65. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  67. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  68. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  69. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  70. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  71. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.4% · 29th percentile

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:dbt-core

Frequently asked(5)

What is CVE-2024-40637?
CVE-2024-40637 is a high-severity vulnerability; its CVE record was published on July 16, 2024. 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…
When was the CVE record for CVE-2024-40637 published?
The CVE record for CVE-2024-40637 was published on July 16, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2024-40637 actively exploited?
CVE-2024-40637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-40637?
CVE-2024-40637 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2024-40637?
A fix for CVE-2024-40637 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-40637

Explore →

Is Your Infrastructure Affected by CVE-2024-40637?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs