{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-14646 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-14646 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-14646 is a medium-severity server-side request forgery vulnerability in Sonatype Nexus Repository Manager, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-14646 and fix it if it is affected.\n\nWhat it is: CVE-2026-14646 is a medium-severity server-side request forgery vulnerability in Sonatype Nexus Repository Manager, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-14646 in the wild and no public exploit code.\n\nAffected product: Sonatype Nexus Repository Manager. 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-2026-14646/ (Markdown: https://insights.sbomify.com/CVE-2026-14646/index.md)","id":"CVE-2026-14646","markdown":"https://insights.sbomify.com/CVE-2026-14646/index.md","name":"CVE-2026-14646","record":{"aliases":["GHSA-jxph-5989-pgpj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nexus Repository 3","requires_auth":"low_privilege","summary":"Attackers with read access can exploit SSRF via HTTP redirects to access internal network resources or cloud metadata, potentially exposing sensitive credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Sonatype","cpe":[{"product":"nexus_repository_manager","vendor":"sonatype"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Nexus Repository 3 did not apply its existing Server-Side Request Forgery (SSRF) protections to HTTP redirect targets returned by proxy repository upstream servers. Any user with read access to a proxy repository backed by an attacker-controlled or compromised upstream server — including an anonymous user, if anonymous access is enabled — could receive a response from an internal network address or cloud metadata endpoint as repository content, potentially exposing sensitive information such as cloud IAM credentials.","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":"Nexus Repository 3 - Server-Side Request Forgery (SSRF) via HTTP Redirect","id":"CVE-2026-14646","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sonatype:nexus_repository_manager","products":["sonatype:nexus_repository_manager"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"onnx onnxruntime old.cc convPoolShapeInference_opset19 out-of-bounds","id":"CVE-2026-14647"},"packages":[],"prev":{"headline":"Nexus Repository 3 - Server-Side Request Forgery (SSRF) via Webhook: Global Capability","id":"CVE-2026-14645"},"products":["Nexus Repository 3"],"published":"2026-07-14","related":[{"cvss_score":9.8,"headline":"Sonatype Nexus Repository Manager Incorrect Access Control","id":"CVE-2019-7238","kev_date_added":"2021-12-10","published":"2019-03-21"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-9629","kev_date_added":null,"published":"2019-07-08"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-17717","kev_date_added":null,"published":"2017-12-17"},{"cvss_score":9.4,"headline":"Nexus Repository 3 - Authenticated Remote Code Execution via Task Property Injection","id":"CVE-2026-3199","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":9.2,"headline":"Nexus Repository 3 - Hardcoded Credential in Internal Database Component","id":"CVE-2026-5189","kev_date_added":null,"published":"2026-04-15"},{"cvss_score":8.9,"headline":"Nexus Repository 3 - Wildcard Privilege Update Self-Escalation to Administrator","id":"CVE-2026-17601","kev_date_added":null,"published":"2026-08-07"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2020-15871","kev_date_added":null,"published":"2020-07-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2026-07-15","vendors":["Sonatype"]},"summary":"Attackers with read access can exploit SSRF via HTTP redirects to access internal network resources or cloud metadata, potentially exposing sensitive credentials.","url":"https://insights.sbomify.com/CVE-2026-14646/"}