Summary
dbt uses a SQLparse version with a high vulnerability
Using a version of sqlparse that has a security vulnerability and no way to update in current version of dbt core. Snyk recommends using sqlparse==0.5 but this causes a conflict with dbt. Snyk states the issues is a recursion error: SNYK-PYTHON-SQLPARSE-6615674.
Details
Dependency conflict error message:
The conflict is caused by:
The user requested sqlparse==0.5
dbt-core 1.7.10 depends on sqlparse<0.5 and >=0.2.3
Resolution was to pin sqlparse >=0.5.0, <0.6.0 in dbt-core, patched in 1.6.13 and 1.7.13.
PoC
From Snyk:
import sqlparse
sqlparse.parse('[' * 10000 + ']' * 10000)
Mitigations
Bump dbt-core 1.6 and 1.7 dependencies to 1.6.13 and 1.7.13 respectively
Impact
Snyk classifies it as high 7.5/10.
GHSA-P72Q-H37J-3HQ7 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.13, 1.7.13); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The bug has been fixed in dbt-core v1.6.13 and dbt-core v1.7.13.
Frequently Asked Questions
- What is GHSA-P72Q-H37J-3HQ7? GHSA-P72Q-H37J-3HQ7 is a high-severity security vulnerability in dbt-core (pip), affecting versions >= 1.6.0, < 1.6.13. It is fixed in 1.6.13, 1.7.13.
- How severe is GHSA-P72Q-H37J-3HQ7? GHSA-P72Q-H37J-3HQ7 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of dbt-core are affected by GHSA-P72Q-H37J-3HQ7? dbt-core (pip) versions >= 1.6.0, < 1.6.13 is affected.
- Is there a fix for GHSA-P72Q-H37J-3HQ7? Yes. GHSA-P72Q-H37J-3HQ7 is fixed in 1.6.13, 1.7.13. Upgrade to this version or later.
- Is GHSA-P72Q-H37J-3HQ7 exploitable, and should I be worried? Whether GHSA-P72Q-H37J-3HQ7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-P72Q-H37J-3HQ7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-P72Q-H37J-3HQ7?
- Upgrade
dbt-coreto 1.6.13 or later - Upgrade
dbt-coreto 1.7.13 or later
- Upgrade