{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2026-42016 in the wild since at least 11 Sep 2026.","fix":"No fix has been published for CVE-2026-42016 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Sep 2026.","what":"CVE-2026-42016 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-42016 and fix it if it is affected.\n\nWhat it is: CVE-2026-42016 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: Yes. Attackers have exploited CVE-2026-42016 in the wild since at least 11 Sep 2026.\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-42016/ (Markdown: https://insights.sbomify.com/CVE-2026-42016/index.md)","id":"CVE-2026-42016","markdown":"https://insights.sbomify.com/CVE-2026-42016/index.md","name":"CVE-2026-42016","record":{"aliases":["GHSA-58cv-8cfm-c8r8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JFrog Artifactory","requires_auth":"low_privilege","summary":"Attackers can escalate privileges in JFrog Artifactory by exploiting incorrect token scope validation during authentication checks.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[{"product":"artifactory","vendor":"jfrog"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"JFrog Artifactory (Self Hosted) versions before 7.133.11 are vulnerable to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"JFrog Artifactory Incorrect Authorization","id":"CVE-2026-42016","indexable":true,"kev":{"dateAdded":"2026-09-11","dueDate":"2026-09-25","knownRansomwareCampaignUse":"Unknown","product":"Artifactory","requiredAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.","vendorProject":"JFrog","vulnerabilityName":"JFrog Artifactory Incorrect Authorization Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"jfrog:artifactory","products":["jfrog:artifactory"],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation via JFrog Worker event token exposure","id":"CVE-2026-42017"},"packages":[],"prev":{"headline":"Gnutls: gnutls: memory corruption due to off-by-one error in pkcs#12 bag handling","id":"CVE-2026-42015"},"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":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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-12","vendors":["jfrog"]},"summary":"Attackers can escalate privileges in JFrog Artifactory by exploiting incorrect token scope validation during authentication checks.","url":"https://insights.sbomify.com/CVE-2026-42016/"}