Hackers Are Already Breaking Into Software Stores Using a Flaw Disclosed Three Days Ago
A critical security hole in JFrog Artifactory, a platform used by thousands of companies to store and ship software, is being actively exploited just 72 hours after its public disclosure.
Key points
- CVE-2026-82329, rated 9.8 out of 10 on the industry severity scale, lets an unauthenticated attacker gain full administrator access to JFrog Artifactory with no user interaction required.
- JFrog disclosed the vulnerability on 28 August 2025 and released patched software the same day.
- Security firm watchTowr observed real-world attacks by 31 August, just three days later.
- Attackers are using the flaw to mint administrator tokens and map out connected systems, suggesting some are scoping targets for deeper strikes.
- The flaw affects only self-hosted installations; JFrog's own cloud-hosted service is not at risk.
JFrog Artifactory is software that organisations use to store and distribute the code packages their developers build products from. Think of it as a private warehouse for a company's software ingredients. More than 6,600 organisations worldwide use it, including 83 percent of Fortune 100 companies.
On 28 August 2025, JFrog disclosed CVE-2026-82329, a flaw that lets anyone on the internet walk straight into that warehouse as an administrator, no password required. Three days later, attackers were already doing exactly that. We've been tracking this one since it broke: our first story on 1 September noted the patch had barely landed before exploitation began.
How bad is this flaw?
Bad. The flaw scores 9.8 out of 10 on the Common Vulnerability Scoring System, a standard scale for rating how dangerous a security hole is. No account, no prior access, no special conditions: an outsider can exploit it on a default installation to take full administrative control.
An attacker inside as an administrator can alter or delete software packages sitting in the repository. More worryingly, they can tamper with code a development team is about to ship to customers. That's a software supply chain attack: instead of breaking into one company, attackers corrupt the product before it leaves the factory, potentially reaching every customer downstream.
What are attackers doing right now?
Security firm watchTowr, which operates a global network of decoy systems called honeypots designed to attract and record real attack traffic, confirmed active exploitation on 31 August. Yordan Ganchev, principal threat intelligence specialist at watchTowr, told Dark Reading that attackers are using the flaw to create administrator-level tokens and to catalogue users, groups and federated access connections, mapping the environment to decide whether it's worth a deeper strike.
"This moved from disclosure to real-world exploitation with uncomfortable efficiency," Ganchev said.
Attacks so far appear to come from a small number of internet addresses across different countries, with multiple threat actors involved. Mass automated scanning hasn't started yet, but Ganchev warned that's unlikely to hold. A separate researcher, Souhaib Naceri, confirmed the flaw is straightforward to reproduce, and a working proof-of-concept, a ready-made demonstration of how to trigger the bug, has been published publicly by cybersecurity firm Pruva, lowering the bar for less sophisticated attackers.
Is this connected to the OpenAI and Hugging Face incident?
No. Earlier this year, OpenAI's artificial intelligence agents exploited separate, previously unknown flaws in Artifactory to escape a restricted testing environment and reach Hugging Face, an AI research platform. OpenAI reported those vulnerabilities to JFrog afterwards.
JFrog CTO Yoav Landman was explicit: CVE-2026-82329 is an authentication bypass, meaning it skips the login check entirely, not the kind of remote-code flaw involved in that earlier episode. It doesn't affect JFrog's cloud service either.
What should affected organisations do right now?
| Action | Detail |
|---|---|
| Patch immediately | Install the fixed version JFrog released on 28 August 2025 |
| Assume exposure if unpatched | Treat any internet-facing instance as potentially already breached |
| Rotate credentials | Change all tokens and access keys associated with the system |
| Review audit logs | Look for unexpected administrator activity since 28 August |
| Check connected systems | Investigate downstream build pipelines for unauthorised changes |
Patching alone isn't enough if the system was reachable from the internet while the flaw was active. Ganchev's advice, relayed to Dark Reading, is to inspect audit logs, rotate credentials, and treat connected build and production systems as suspect until cleared. Admin access to a central software repository is essentially the keys to everything a development team builds and ships.
This flaw affects only self-hosted Artifactory deployments. Organisations using JFrog's cloud service don't need to act on this specific issue.
