CVE-2022-39351: Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the

Q: How do I fix CVE-2022-39351?

dependency-track: upgrade to 4.6.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-39351 being exploited?

CVE-2022-39351 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-39351 affect?

CVE-2022-39351 affects dependency-track. Severity is medium (CVSS 4.4). Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.6.0, performing an API request using a valid API key with insufficient permissions caus

Q: How urgent is CVE-2022-39351?

Priority 18/100. No elevated risk signals yet.

Routine

MEDIUM 4.4UPGRADE

CVE-2022-39351 is a medium-severity flaw (CVSS 4.4) affecting dependency-track. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.6.0, performing an API request using a valid API key with insufficient permissions causes the API key to be written to Dependency-Track's audit log in clear text. Actors with access to the audit log can exploit this flaw to gain access to valid API keys. The issue has been fixed in Dependency-Tra

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.4 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-312
Published	2022-10-25
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: owasp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-25 17:15 UTCPublished CVE record published
2026-06-17 04:58 UTCUpdated Record last modified

owasp dependency-track UPGRADE

Affected: < 4.6.0

Fixed in: 4.6.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dependency-track || rpm -q dependency-track || dependency-track --version

2. UPGRADE to 4.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dependency-track

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dependency-track

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-39351?

dependency-track: upgrade to 4.6.0. Exact commands for each OS are on this page.

Is CVE-2022-39351 being exploited?

CVE-2022-39351 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-39351 affect?

CVE-2022-39351 affects dependency-track. Severity is medium (CVSS 4.4). Dependency-Track is a Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.6.0, performing an API request using a valid API key with insufficient permissions caus

How urgent is CVE-2022-39351?

Priority 18/100. No elevated risk signals yet.

Related CVEs

CVE-2019-1020007 MEDIUM 5.4 UPGRADE Dependency-Track before 3.5.1 allows XSS.

References

← Back to latest CVEs