DependencyTrack dependency-track up to 4.13.4 .NET insufficiently protected credentials

Summaryinfo

A vulnerability was found in DependencyTrack dependency-track up to 4.13.4. It has been classified as problematic. This affects an unknown part of the component .NET Component. Performing a manipulation results in insufficiently protected credentials. This vulnerability is cataloged as CVE-2025-61776. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in DependencyTrack dependency-track up to 4.13.4. This affects an unknown code block of the component .NET Component. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-61776 since 09/30/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

Upgrading to version 4.13.5 eliminates this vulnerability. The upgrade is hosted for download at github.com.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-32901). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• DependencyTrack

Name

• dependency-track

Version

• 4.13.0
• 4.13.1
• 4.13.2
• 4.13.3
• 4.13.4

Website

• Product: https://github.com/DependencyTrack/dependency-track/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion