Every CVESearch/Get API key

GHSA-j4g3-3q8x-jxqp

dbt-core's secret env vars written to package-lock.json in plaintext

3.2 LowFix available

GHSA-j4g3-3q8x-jxqp is a low vulnerability (CVSS 3.2) in dbt-core, published December 8, 2023. No source lists public exploit code. Fixed in dbt-core 1.7.3.

What does this mean?
Severity
3.2 LowCVSS 3.1, GitHub Advisories
Exploit chance
UnscoredNo EPSS score yet
Exploitation
None knownNot on CISA’s or ENISA’s lists
Fixed in
1.7.3dbt-core +1 more

Description

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.

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.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
Required

What an attacker can affect

Confidentiality
Low
Integrity
None
Availability
None

Affected packages

Affected packages
PackageAffectedFixed
dbt-core
PyPI
1.7.0 up to 1.7.3
1.7.3
dbt-core
PyPI
1.7.0 up to 1.7.3, plus listed versions
1.7.11.7.2
1.7.3

What each source reports

GitHub Advisories Score used3.2

dbt-core's secret env vars written to package-lock.json in plaintext

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.

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.

Record
GHSA-j4g3-3q8x-jxqp
CVSS 3.1
3.2 LowCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N
Weakness
CWE-315
Updated
2026-11-02
OSV3.2

dbt-core's secret env vars written to package-lock.json in plaintext

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.

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.

Record
GHSA-j4g3-3q8x-jxqp
CVSS 3.1
3.2 LowCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N
Weakness
CWE-315
Updated
2026-11-02

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

MoveEnter Open