{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42017 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42017 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42017 is a high-severity vulnerability in Jfrog Artifactory, published on 27 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-42017 and fix it if it is affected.\n\nWhat it is: CVE-2026-42017 is a high-severity vulnerability in Jfrog Artifactory, published on 27 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-42017 in the wild and no public exploit code.\n\nAffected product: Jfrog Artifactory. 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-42017/ (Markdown: https://insights.sbomify.com/CVE-2026-42017/index.md)","id":"CVE-2026-42017","markdown":"https://insights.sbomify.com/CVE-2026-42017/index.md","name":"CVE-2026-42017","record":{"aliases":["GHSA-g554-2364-r9j6"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JFrog Artifactory","requires_auth":"low_privilege","summary":"A lower-privileged user can obtain privileged authorization tokens via an event-handling flaw, enabling privilege escalation in JFrog Artifactory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[{"product":"artifactory","vendor":"jfrog"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An event-handling weakness in JFrog Artifactory could expose privileged authorization material to a lower-privileged user under specific conditions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation via JFrog Worker event token exposure","id":"CVE-2026-42017","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"jfrog:artifactory","products":["jfrog:artifactory"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"JFrog Artifactory Improper Authentication","id":"CVE-2026-42018"},"packages":[],"prev":{"headline":"JFrog Artifactory Incorrect Authorization","id":"CVE-2026-42016"},"products":["artifactory"],"published":"2026-07-27","related":[{"cvss_score":9.8,"headline":"JFrog Artifactory Improper Authentication","id":"CVE-2026-82329","kev_date_added":"2026-09-02","published":"2026-08-28"},{"cvss_score":8.1,"headline":"JFrog Artifactory Incorrect Authorization","id":"CVE-2026-42016","kev_date_added":"2026-09-11","published":"2026-07-27"},{"cvss_score":7.5,"headline":"JFrog Artifactory Improper Authentication","id":"CVE-2026-42018","kev_date_added":"2026-09-11","published":"2026-08-12"},{"cvss_score":5.3,"headline":"JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory","id":"CVE-2026-66384","kev_date_added":"2026-08-27","published":"2026-08-12"},{"cvss_score":9.8,"headline":"JFrog Artifactory does not enforce default admin password change","id":"CVE-2019-17444","kev_date_added":null,"published":"2020-10-12"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2018-19971","kev_date_added":null,"published":"2019-04-16"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-9733","kev_date_added":null,"published":"2019-04-11"}],"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-07-27","vendors":["jfrog"]},"summary":"A lower-privileged user can obtain privileged authorization tokens via an event-handling flaw, enabling privilege escalation in JFrog Artifactory.","url":"https://insights.sbomify.com/CVE-2026-42017/"}