Quick answers
- Is CVE-2026-42016 exploited in the wild?
- Yes. CVE-2026-42016 is known to be exploited in the wild, first recorded on 11 September 2026. Treat it as urgent.
- How severe is CVE-2026-42016?
- Critical severity, with a CVSS score of 8.1, published 27 July 2026.
- Which products and versions are affected?
- JFrog Artifactory < 7.133.11.
- Is there a fix for CVE-2026-42016?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-42016 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-42016?
- Check whether you run JFrog Artifactory at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
JFrog Artifactory contains an incorrect authorization vulnerability where the token validation logic checks the signature and issuer but fails to properly validate the token's scope constraints. This allows an authenticated attacker with a valid token to perform actions and access resources beyond the scope granted by their token. The vulnerability is exploitable by any user with a valid token, without requiring administrative credentials. An attacker can leverage this to escalate privileges, access restricted artifacts, modify repositories, or perform other privileged operations. The vulnerability has been observed actively exploited in the wild.
Affected products
- JFrog Artifactory
Timeline
- 2026-09-11: disclosed
- 2026-09-11: exploited: Actively exploited in the wild