CVE-2026-42016: high-severity vulnerability in jfrog artifactory
Incorrect authorization validation of user token in JFrog Artifactory allows Privilege Escalation
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
Prioritize patching. It under exploitation confirmed by CISA and has an official Brazilian government alert.
Brazil's federal government published an alert, recommendation or bulletin that cites this vulnerability.
- CISC Gov.br · 16 Sep 2026Boletim do CISC de Vulnerabilidadesread on gov.br ↗
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.
JFrog Artifactory fails to properly check user permissions when validating tokens, allowing attackers to gain higher privileges than they should have. This could let someone access or modify files they shouldn't be able to reach.
The vulnerability stems from improper authorization validation in JFrog Artifactory versions before 7.133.11, where the authentication mechanism validates token signature/issuer but fails to enforce token scope restrictions. An attacker with a valid token can escalate privileges by bypassing scope validation, potentially gaining unauthorized access to protected resources or administrative functions.
In the same product, most dangerous first.