CVE-2026-42016 — Artifactory
HIGHCVE-2026-42016 is a high-severity (CVSS 8.1) CWE-863 vulnerability in jfrog artifactory. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-09-11) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
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.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-09-11. Federal agencies were required to remediate by 2026-09-25.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-42016.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-42016 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 398,142 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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.
Affected Products
artifactoryjfrogDetection & mitigation playbook
Vendor / applianceDetect
Inventory every jfrog artifactory deployment and check each version against the affected-products list above.
Fix
Apply the jfrog artifactory security patch or hotfix for CVE-2026-42016 on the affected version, following the vendor advisory for your exact build.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-42016 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.