Summary
dbt-core's secret env vars written to package-lock.json in plaintext
Mitigations
Remove any git URLs with plaintext secrets from package-lock.yml file(s) on servers, workstations, or in source control. Rotate any tokens that have been written to version-controlled files.
Impact
When used to pull source code from a private repository using a Personal Access Token (PAT), some versions of dbt-core write a URL with the PAT in plaintext to the package-lock.yml file.
GHSA-J4G3-3Q8X-JXQP has a CVSS score of 3.2 (Low). The vector is requires local access, low privileges required, and user interaction required. 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.7.3); 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.7.3.
Frequently Asked Questions
- What is GHSA-J4G3-3Q8X-JXQP? GHSA-J4G3-3Q8X-JXQP is a low-severity security vulnerability in dbt-core (pip), affecting versions >= 1.7.0, < 1.7.3. It is fixed in 1.7.3.
- How severe is GHSA-J4G3-3Q8X-JXQP? GHSA-J4G3-3Q8X-JXQP has a CVSS score of 3.2 (Low). 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-J4G3-3Q8X-JXQP? dbt-core (pip) versions >= 1.7.0, < 1.7.3 is affected.
- Is there a fix for GHSA-J4G3-3Q8X-JXQP? Yes. GHSA-J4G3-3Q8X-JXQP is fixed in 1.7.3. Upgrade to this version or later.
- Is GHSA-J4G3-3Q8X-JXQP exploitable, and should I be worried? Whether GHSA-J4G3-3Q8X-JXQP 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-J4G3-3Q8X-JXQP 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-J4G3-3Q8X-JXQP? Upgrade
dbt-coreto 1.7.3 or later.