CVE-2026-42016
JFrog Artifactory Incorrect Authorization Vulnerability
Description
CVE-2026-42016 is a high-severity incorrect authorization vulnerability in JFrog Artifactory (Self Hosted) that enables privilege escalation. Artifactory versions before 7.133.11 validate only a token's signature and issuer but never check the token's scope, so an authenticated user holding a legitimate low-privilege token can reach resources and operations that the token was never meant to authorize. Because Artifactory is the artifact repository at the centre of many software supply chains, this privilege escalation vulnerability puts build artifacts, container images and repository credentials at risk of disclosure and tampering. CVE-2026-42016 carries a CVSS score of 8.1, has been observed exploited in the wild, and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog with a remediation deadline of 25 September 2026.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| jfrog | artifactory | < 7.133.11 |
Multiple CVSS Assessments
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases(Release Notes)
- https://docs.jfrog.com/releases/docs/jfrog-security-advisories(Vendor Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42016(US Government Resource)
- https://www.wiz.io/blog/artifactory-under-attack-in-the-wild-exploitation-of-cve-2026-42016-cve-2026-4201(Third Party Advisory)
Weakness Type
CWE-863: Incorrect Authorization
Incorrect authorization occurs when a product does perform an authorization check, but implements it incorrectly — unlike missing authorization, the check exists yet reaches the wrong conclusion. In CVE-2026-42016 Artifactory validates that a token is correctly signed and issued, and then treats that as sufficient, never evaluating whether the token's scope actually covers the requested operation.
Learn more: CWE-863 — Incorrect Authorization
Impact Analysis
CVE-2026-42016 is remotely exploitable over the network with low attack complexity and no user interaction, and needs only low privileges — any account able to obtain a valid Artifactory token can attempt the escalation. A successful attack results in high confidentiality and high integrity impact, meaning an attacker can read private repositories and modify or replace stored artifacts, while availability is not directly affected. In a CI/CD context that combination is particularly dangerous: tampering with a widely consumed artifact in Artifactory turns a single privilege escalation into a downstream supply-chain compromise. Rated CVSS 8.1 (High) with an EPSS score of roughly 0.9% (57th percentile), the statistical exploitation estimate is moderate, but Wiz has published analysis of in-the-wild exploitation of CVE-2026-42016 and CISA has added it to the KEV catalog, so the real-world likelihood is considerably higher than the EPSS figure suggests.
Exploit Maturity
CISA has confirmed active exploitation of CVE-2026-42016 by adding it to the Known Exploited Vulnerabilities catalog, and Wiz has published a public analysis documenting in-the-wild exploitation of this vulnerability alongside a companion Artifactory flaw — see Wiz Research: Artifactory under attack. That write-up means the exploitation technique is publicly described, which materially lowers the barrier for follow-on attackers even where no packaged exploit tool is published. The EPSS score of about 0.9% (57th percentile) is a poor guide here, since EPSS lags confirmed targeted exploitation of enterprise software. The KEV ransomware flag is "Unknown", but given Artifactory's position in software supply chains, exploitation should be assumed to be ongoing and patching treated as urgent.
Remediation
- Follow the CISA KEV required action. Apply mitigations in accordance with JFrog's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date is 25 September 2026.
- Upgrade JFrog Artifactory Self Hosted to version 7.133.11 or later. All self-hosted releases below 7.133.11 are affected; consult the JFrog self-managed release notes and security advisories for the correct upgrade path for your branch.
- Rotate all Artifactory access tokens after patching. Because the flaw lets an existing valid token be used beyond its scope, assume issued tokens may have been abused and revoke and reissue access tokens, identity tokens and any credentials embedded in CI/CD pipelines.
- Restrict network exposure of the Artifactory instance. Place Artifactory behind a reverse proxy or VPN and limit access to trusted build networks and administrative ranges rather than exposing the self-hosted instance directly to the internet.
- Hunt for evidence of abuse and harden authorization long term. Review Artifactory access and audit logs for token use against repositories outside the token's intended scope, for unexpected artifact uploads or overwrites, and for new permission targets; then enforce authorization through centrally managed, well-tested checks that evaluate scope on every request, apply least-privilege permission targets, and add defence in depth around the repositories used by production builds.
Technical Details
CVE-2026-42016 is an incorrect authorization flaw (CWE-863) in the token-validation path of JFrog Artifactory Self Hosted: the server verifies the cryptographic signature and the issuer of a presented token and accepts the request on that basis, without evaluating the scope claim that is supposed to bound what the token may do. An attacker who legitimately possesses a narrowly scoped token — for example a read-only token for a single repository — can therefore present it against privileged operations, and the server honours it because the signature check passes. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N reflects that the attack is network-reachable, requires no special conditions and no user interaction, needs only low privileges, and yields high confidentiality and integrity impact without touching availability. Since the vulnerable logic sits in token validation rather than in any single endpoint, every API surface that trusts the token inherits the weakness, which is why the flaw is described as privilege escalation rather than as a single broken endpoint.
Frequently Asked Questions
Is CVE-2026-42016 being actively exploited?
Yes. CISA added CVE-2026-42016 to its Known Exploited Vulnerabilities catalog with a remediation due date of 25 September 2026, and security vendor Wiz has published research documenting in-the-wild exploitation of the flaw. Organisations running affected self-hosted Artifactory instances should treat this as an active incident risk, not a theoretical one.
What products are affected by CVE-2026-42016?
The vulnerability affects JFrog Artifactory Self Hosted in all versions before 7.133.11. JFrog's self-managed release notes and security advisories list the fixed builds; cloud-hosted Artifactory customers should confirm their instance version against the vendor advisory.
How do I fix CVE-2026-42016?
Upgrade JFrog Artifactory Self Hosted to 7.133.11 or later, then rotate every access token and CI/CD credential issued by the instance, because previously issued tokens may have been used beyond their scope. Restrict network access to Artifactory and review audit logs for cross-scope token use and unexpected artifact writes.
How severe is CVE-2026-42016?
CVE-2026-42016 is rated High with a CVSS 3.1 base score of 8.1. It is network-exploitable with low complexity, needs only a low-privileged token and no user interaction, and delivers high confidentiality and integrity impact; the EPSS score sits near the 57th percentile, but confirmed KEV-listed exploitation and public exploitation research make it a top-priority fix.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.