Dependency-Track possibly discloses private NuGet repository credentials to api.nuget.org
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-61776
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 03:13 UTC · Revision 1
Source evidence
Dependency-Track possibly discloses private NuGet repository credentials to api.nuget.org
core-osv · Original sourcePublished 7 Oct 2025, 18:57 UTC
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.
osv:CVE-2025-61776
Complete source record
{
"id": "18273cc162cd94c01a0bc08d0e38f44c837575eec29531021b00de5e64538ba2",
"url": "https://osv.dev/vulnerability/CVE-2025-61776",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Dependency-Track possibly discloses private NuGet repository credentials to api.nuget.org",
"summary": "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.",
"evidence": "osv:CVE-2025-61776",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2025-61776",
"aliases": [
"CVE-2025-61776",
"GHSA-83g2-vgqh-mgxc"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/dependencytrack/dependency-track",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "54deee037fd1581481ee51b15c967b795ceba567"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "4.13.5"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "54deee037fd1581481ee51b15c967b795ceba567"
}
],
"source": "REFERENCES_TAG",
"original_tag": "4.13.5"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "4.13.5"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"4.13.4",
"4.13.3",
"4.13.2",
"4.13.1",
"4.13.0",
"4.12.0",
"4.11.0",
"4.10.0",
"4.9.0",
"4.8.0",
"4.6.0",
"4.5.0",
"4.4.1",
"4.4.2",
"4.4.0",
"4.3.6",
"4.3.5",
"4.3.4",
"4.3.3",
"4.3.2",
"4.3.1",
"4.3.0",
"4.2.2",
"4.2.1",
"4.2.0",
"4.1.0",
"4.0.1",
"4.0.0",
"4.0.0-rc.1",
"4.0.0-beta.4",
"4.0.0-beta.3",
"4.0.0-beta.1",
"4.0.0-SNAPSHOT",
"3.8.0",
"3.7.1",
"3.7.0",
"3.6.1",
"3.6.0",
"3.5.1",
"3.5.0",
"3.4.1",
"3.4.0",
"3.3.1",
"3.3.0",
"3.2.2",
"3.2.1",
"3.2.0",
"3.1.1",
"3.1.0",
"3.0.4",
"3.0.3",
"3.0.1",
"3.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-61776.json"
}
}
],
"modified": "2026-10-28T02:30:32.861138339Z",
"provider": "osv",
"references": [
"https://github.com/DependencyTrack/dependency-track/releases/tag/4.13.5",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/61xxx/CVE-2025-61776.json",
"https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-83g2-vgqh-mgxc",
"https://nvd.nist.gov/vuln/detail/CVE-2025-61776"
],
"provider_metadata": {
"cwe_ids": [
"CWE-522"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/61xxx/CVE-2025-61776.json"
}
},
"related_cves": [
{
"value": "CVE-2025-61776",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 499963,
"published_at": "2025-10-07T18:57:06.035+00:00"
}