Quick answers
- Is CVE-2026-65616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65616 being exploited in the wild.
- How severe is CVE-2026-65616?
- High severity, with a CVSS score of 8.8, published 27 July 2026.
- Which products and versions are affected?
- JFrog Artifactory Self-Managed < 7.146.27.
- Is there a fix for CVE-2026-65616?
- A patch was published on 2026-07-27: Fixed in version 7.146.27 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-65616 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-65616?
- Check whether you run JFrog Artifactory Self-Managed 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
The vulnerability is classified as an improper verification of cryptographic signatures (CWE-347) within the refresh token mechanism. Due to incorrect authorization validation during the token signature process, an authenticated user with low privileges can generate or obtain a validly signed administrator-level token. This is a network-based attack that requires basic user authentication but no user interaction. Successful exploitation results in full privilege escalation to the administrator role, granting the attacker complete control over the JFrog Platform. The issue is addressed in Artifactory version 7.146.27 and later.
Affected products
- JFrog Artifactory Self-Managed < 7.146.27
Timeline
- 2026-07-27: disclosed
- 2026-07-27: advisory
- 2026-07-27: patched: Fixed in version 7.146.27