{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-17593 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-17593 is a high-severity code injection vulnerability in Sonatype Nexus Repository Manager, published on 7 Aug 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-17593 and fix it if it is affected.\n\nWhat it is: CVE-2026-17593 is a high-severity code injection vulnerability in Sonatype Nexus Repository Manager, published on 7 Aug 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-17593 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-17593/ (Markdown: https://insights.sbomify.com/CVE-2026-17593/index.md)","id":"CVE-2026-17593","markdown":"https://insights.sbomify.com/CVE-2026-17593/index.md","name":"CVE-2026-17593","record":{"aliases":["GHSA-rw8g-2688-625j","MINI-9794-c5c6-6rvc","MINI-pr4g-jcx3-qf9w"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Nexus Repository","requires_auth":"low_privilege","summary":"An attacker with settings update permissions can inject arbitrary class names to execute code or cause authentication lockouts in Nexus Repository.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Sonatype","cpe":[{"product":"nexus_repository_manager","vendor":"sonatype"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-470","name":"Use of Externally-Controlled Input to Select Classes or Code"}],"description":"An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm identifiers through an internal configuration API that did not validate them against the set of registered realms. Because unrecognized entries were persisted and re-evaluated on every realm load via a legacy code path, this could result in unintended code executing inside the Nexus Repository process, and in some cases a persistent authentication lockout that was not visible through the administrative UI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nexus Repository - Arbitrary Class Instantiation via Unsafe Realm Configuration","id":"CVE-2026-17593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sonatype:nexus_repository_manager","products":["sonatype:nexus_repository_manager"],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Nexus Repository 3 - Authorization Bypass in Repository Creation","id":"CVE-2026-17594"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2026-17592"},"products":["Nexus Repository"],"published":"2026-08-07","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":"total"},"state":"PUBLISHED","updated":"2026-08-08","vendors":["Sonatype"]},"summary":"An attacker with settings update permissions can inject arbitrary class names to execute code or cause authentication lockouts in Nexus Repository.","url":"https://insights.sbomify.com/CVE-2026-17593/"}