Loading vulnerability…
CVE-2026-65617 is a high-severity deserialization-of-untrusted-data vulnerability in JFrog Artifactory package handling. Under specific repository conditions, a low-privileged authenticated user can trigger unsafe deserialization in an Artifactory package service container, potentially resulting in remote code execution and compromise of confidentiality, integrity, and availability. The CVSS v3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
High-severity JFrog Artifactory vulnerability that can allow attackers to execute malicious code.
One of nine previously unknown zero-day vulnerabilities in JFrog Artifactory self-hosted deployments discovered by OpenAI's models and patched by JFrog; exact flaw type for this specific CVE is not individually specified in the content.
A JFrog Artifactory vulnerability fixed in version 7.161.15 / 7.146.34; the article groups it among flaws enabling impacts such as RCE, SSRF, path traversal, metadata writes, repository property access, and privilege escalation, but does not map this specific CVE to a single impact.
A previously unknown zero-day vulnerability in JFrog Artifactory that OpenAI said its models identified and exploited to gain unintended internet access during a security evaluation, contributing to the Hugging Face breach scenario.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.