JFrog disclosed CVE-2026-42016, a high-severity privilege-escalation vulnerability in Artifactory Self-Hosted caused by incorrect authorization validation of user tokens. The flaw affects versions before 7.133.11 and stems from token checks that validate the signature and issuer but do not verify the token scope, allowing an authenticated user with low privileges to gain elevated access. The issue is tracked as CWE-863 and carries a CVSS v3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, indicating high confidentiality and integrity impact with no direct availability impact.
JFrog’s self-managed release documentation lists 7.133.11 as the fixed version for affected deployments, and organizations running on-premises Artifactory are expected to prioritize upgrades. Because exploitation requires only valid low-privilege access and no user interaction, the vulnerability raises the risk of unauthorized access to repositories, artifacts, and administrative functions in environments that have not yet patched.

Get the actors, campaigns, and ATT&CK mapping behind it.
1 event from the most recent confirmed update back to the earliest known activity.
A new vulnerability, CVE-2026-42016, was recorded on July 27, 2026 for JFrog Artifactory Self Hosted. The flaw affects versions before 7.133.11 and allows privilege escalation because token validation checks the signature and issuer but not the token scope.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.