Skip to main content
CVE-2025-61776VulnerabilityPublished

CVE-2025-61776: DependencyTrack dependency-track · Insufficiently Protected Credentials

Affects DependencyTrack dependency-trackSource CVE Database V5

0

Not known to be exploited · CVSS 4.7 Medium : upgrade to 4.13.5 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.13.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade DependencyTrack dependency-track to 4.13.5.

Affected software

ProductAffectedFixed in
DependencyTrack dependency-trackAffected
  • <4.13.5
Fixed in
  • 4.13.5

AI-suggested

European organizations should immediately upgrade Dependency-Track instances to version 4.13.5 or later to remediate the vulnerability. Until patching is complete, disable all custom NuGet repositories configured with authentication to prevent credential leakage. Organizations must invalidate and rotate any credentials previously used with these custom repositories to mitigate the risk of unauthorized access. Review and audit Dependency-Track configurations to ensure no unintended credential exposure occurs. Implement network monitoring to detect unusual outbound traffic to api.nuget.org or other unexpected endpoints. Enforce strict access controls and logging around Dependency-Track and NuGet repository credentials. Additionally, consider isolating Dependency-Track instances within secure network segments to limit exposure. Educate development and DevOps teams about the risk and ensure secure handling of repository credentials. Finally, integrate Dependency-Track updates into regular patch management processes to prevent recurrence.

Description

Dependency-Track is a component analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.13.5, Dependency-Track may send credentials meant for a private NuGet repository to `api.nuget.org` via the HTTP `Authorization` header, and may disclose names and versions of components marked as internal to `api.nuget.org`. This can happen if the Dependency-Track instance contains .NET components, a custom NuGet repository has been configured, the custom repository has been configured with authentication credentials, and the repository server does not provide `PackageBaseAddress` resource in its service index. The issue has been fixed in Dependency-Track 4.13.5. Some workarounds are avaialble. Disable custom NuGet repositories until the patch has been applied, invalidate the previously used credentials, and generate new credentials for usage after the patch has been applied.

References

Community reviews

Loading reviews…