CVE-2026-42016: JFrog Artifactory Incorrect Authorization
JFrog Artifactory · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-11.
- CVSS v3.1 (CVE record)
- 8.1
- high
- EPSS (exploit probability, 30 days)
- 8.6%
- higher than 95.2% of all CVEs
- Added to CISA KEV
- 2026-09-11
- US federal due date 2026-09-25
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-42016 explained
CVE-2026-42016 is an incorrect authorization flaw in JFrog Artifactory (Self Hosted) versions before 7.133.11. Artifactory validates a token's signature and issuer but not its scope, which allows privilege escalation. CISA lists it as known to be exploited, so affected servers need prompt attention.
Impact
An attacker with low privileges can escalate those privileges over the network. No user interaction is required, and attack complexity is low. Successful exploitation can cause high loss of confidentiality and integrity. CISA rates the technical impact as total, meaning full control of the affected component or full disclosure of its data. CISA does not consider it automatable at scale. Attackers are known to exploit it. Ransomware use is unknown.
Who is affected
The CVE record lists JFrog Artifactory (Self Hosted) versions before 7.133.11 as affected (< 7.133.11). Version 7.133.11 contains the fix. The affected and fixed versions are as published in the CVE record by its CNA, JFROG.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
CISA notes
- docs.jfrog.com/releases/docs/jfrog-security-advisories
- docs.jfrog.com/releases/docs/artifactory-self-managed-rel…
- BOD 26-04: cisa.gov/news-events/directives/bod-26-04-prioritizing-se…
- Forensics Triage Requirements: cisa.gov/news-events/directives/bod-26-04-implementation-…
- nvd.nist.gov/vuln/detail/CVE-2026-42016
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- jfrog artifactoryAffectedFixed in
- < 7.133.11
- 7.133.11
| Product | Affected | Fixed in |
|---|---|---|
| jfrog artifactory |
|
|
How to fix it
- Update to a fixed version: 7.133.11.
- Vendor advisory: docs.jfrog.com/releases/docs/jfrog-security-advisories
- CISA's deadline for US federal agencies: 2026-09-25 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade all self-hosted JFrog Artifactory instances to version
7.133.11or later. - Follow the JFrog vendor advisory and apply any mitigations it describes.
- Restrict network access to Artifactory, especially from the internet, until it is upgraded.
- Review and revoke or rotate access tokens, and audit accounts for unexpected privilege changes.
- Check logs for signs of compromise, in line with CISA's forensics triage requirements.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-863 Incorrect Authorization
Questions about CVE-2026-42016
- Is CVE-2026-42016 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-11, with a US federal due date of 2026-09-25. Whether it is used in ransomware campaigns is unknown.
- Which version fixes the vulnerability?
- JFrog Artifactory (Self Hosted)
7.133.11contains the fix. All versions before7.133.11are affected. - Does an attacker need an account?
- Yes. The CVSS vector requires low privileges, so the attacker needs some existing access. The flaw lets that attacker escalate privileges because Artifactory does not check a token's scope.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.