Live › vulnerability › CVE-2026-42016
Go to dashboardArtifactory Self-Hosted checks a token's signature and issuer but not its scope, so a low-privileged token can be exchanged for an admin-scoped one (CWE-863). Wiz saw it exploited in the wild from 15 Aug to 8 Sep 2026, chained with CVE-2026-42018 (anonymous token leak). The chain went from an unauthenticated request to an admin token in two steps. Attackers then created admin accounts, dropped Groovy plugins and installed a Rust backdoor. CISA added it to KEV on 11 Sep 2026.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
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.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| JFrog Artifactory (Self-Hosted) | vendor | < 7.133.11 | 7.133.11 |
| jfrog artifactory | vendor | < 7.133.11 | 7.133.11 |
| JFrog Artifactory | vendor | – | – |
7.133.11 is affectedtoken:anonymous that create users (PUT /api/security/users/ or /access/api/ui/users/), unknown admin users, and unexpected .groovy files in $JFROG_HOME/var/etc/artifactory/plugins/7.133.11 or laters advisory lists only <7.133.11' for this CVE, but the sibling CVE-2026-42018 and the later ones are fixed in later releases per branch (7.146.x, 7.161.x), so move to the latest release on your branchEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
JFrog Artifactory contains an incorrect authorization vulnerability that leads to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.
CISA required action: 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-42016")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.