{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-61776 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-61776 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61776 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-61776 and fix it if it is affected.\n\nWhat it is: CVE-2025-61776 is a medium-severity vulnerability in DependencyTrack dependency-track, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-61776 in the wild and no public exploit code.\n\nAffected product: DependencyTrack dependency-track. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61776/ (Markdown: https://insights.sbomify.com/CVE-2025-61776/index.md)","id":"CVE-2025-61776","markdown":"https://insights.sbomify.com/CVE-2025-61776/index.md","name":"CVE-2025-61776","record":{"aliases":["GHSA-83g2-vgqh-mgxc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Dependency-Track","requires_auth":"none","summary":"Dependency-Track may leak private NuGet repository credentials and internal component details to api.nuget.org under specific configuration conditions.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Dependency-Track possibly discloses private NuGet repository credentials to api.nuget.org","id":"CVE-2025-61776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"FlagForge Allows Unauthenticated Badge Template API Access","id":"CVE-2025-61777"},"packages":[],"prev":{"headline":"Vickey's unexpired email confirmation link can be reused to send repeated confirmation emails","id":"CVE-2025-61775"},"products":["dependency-track"],"published":"2025-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-07","vendors":["DependencyTrack"]},"summary":"Dependency-Track may leak private NuGet repository credentials and internal component details to api.nuget.org under specific configuration conditions.","url":"https://insights.sbomify.com/CVE-2025-61776/"}