Vulnerability in Dependency-Track (CVE-2025-61776)
Summary
Vulnerability in Dependency-Track (CVE-2025-61776). Risk of unauthorized operations or information disclosure. Exploitable via api.nuget.org.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-61776 has been found in Dependency-Track.
Attackers can target a specific entry point like api.nuget.org over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Dependency-Track CVE-2025-61776" on the vendor's site.
CVE-2025-61776 (Dependency-Track) — CWE-522 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: api.nuget.org / Authorization / PackageBaseAddress
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in Dependency-Track. Attackers reach the vulnerable code path via api.nuget.org without authentication.
Check the vendor advisory for the affected versions of Dependency-Track. Attack surface: api.nuget.org / Authorization / PackageBaseAddress.
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Dependency-Track' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Dependency-Track' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Dependency-Trackを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。