dbt-core's secret env vars written to package-lock.json in plaintext
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### 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. ### Patches The bug has been fixed in [dbt-core v1.7.3](https://github.com/dbt-labs/dbt-core/releases/tag/v1.7.3). ### 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | dbt-core (PyPI) | 1.7.0 to before 1.7.3 | 1.7.3 | Patch available | GHSA-j4g3-3q8x-jxqp |
- dbt-core (PyPI) Vendor— Affected 1.7.0 to before 1.7.3 Fixed in 1.7.3 Patch available GHSA-j4g3-3q8x-jxqp
Remediation
- Fix · GHSA-j4g3-3q8x-jxqp dbt-core (PyPI) Fixed in 1.7.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-j4g3-3q8x-jxqp
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences