Targets JFrog Artifactory, a widely used artifact repository; deserialization flaw lets low-privileged users impact confidentiality, integrity and availability of repos and CI/CD artifacts.
CVE-2026-65617
Deserialization in JFrog Artifactory enables low-privilege actors to escalate and tamper with artifacts.
Is CVE-2026-65617 being exploited?
Not confirmed. CVE-2026-65617 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.
How severe is CVE-2026-65617?
CVE-2026-65617 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65617?
Yes. A fix has been recorded for CVE-2026-65617. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65617 affect?
CVE-2026-65617 affects JFrog Artifactory (package handling / repository components). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65617?
Restrict repo write access, audit artifacts and logs, and apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A low-privileged user can exploit deserialization to escalate privileges, modify/exfiltrate artifacts, or disrupt repository services.
Patch when possible
- affected< 7.111.18
- affected>= 7.117.0 and < 7.117.25
- affected>= 7.125.0 and < 7.125.18
- affected>= 7.133.0 and < 7.133.27
- affected>= 7.146.0 and < 7.146.34
- affected>= 7.161.0 and < 7.161.15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.