This appears to confirm that the packaging proxy they were using for the research machine that their agent broke out of was Artifactory, the same software they use in production.<p>(You can tell they use it in production by asking regular ChatGPT to run "env | grep ARTIFAC" in its container environment.)<p>Hard to decipher which vulnerability was responsible, or if it took several.<p><a href="https://www.cve.org/CVERecord?id=CVE-2026-66014" rel="nofollow">https://www.cve.org/CVERecord?id=CVE-2026-66014</a> (reported by Amy Burnett, OpenAI) looks suspicious:<p>> JFrog Artifactory contains an authentication handling weakness in internal request processing that, under specific conditions, may allow an attacker to escalate privileges beyond the intended access level.<p>Also <a href="https://www.cve.org/CVERecord?id=CVE-2026-65925" rel="nofollow">https://www.cve.org/CVERecord?id=CVE-2026-65925</a> (reported by Matthew Bryant, OpenAI):<p>> A user with JFrog Artifactory Cargo remote repository read access could make Artifactory request unintended URLs and return the response.
The part I find the strangest in that whole affair is the way OpenAI is framing a felony (their systems accessed other company servers and exfiltrated private data, for multiple days, by exploiting vulnerabilities) as a successful partnership with jfrog and huggingface.<p>Aren’t we now in a situation where a large AI vendor can engineer a similar situation against another corporation, then if caught committing a crime, they come up with the same “wow, look at what the agent did, thanks to our crazy rebellious AI the world is now safer”?
So that is the package caching proxy from the OpenAI/Huggingface fiasco!<p>However, many questions remain. JFrog positions itself as a vibe coding and AI security (!) company:<p><a href="https://cybersecurityasia.net/jfrog-nvidia-secure-agentic-ai-development/" rel="nofollow">https://cybersecurityasia.net/jfrog-nvidia-secure-agentic-ai...</a><p>JFrog's own vibe code scanner failed:<p><a href="https://jfrog.com/blog/jfrog-introduces-ai-generated-code-validation/" rel="nofollow">https://jfrog.com/blog/jfrog-introduces-ai-generated-code-va...</a><p>Given the feature explosion and chaos in the Artifactory cache, it is likely vibe coded and hence full of primitive security vulnerabilities.<p>JFrog is spinning this as an <i>AI victory</i> together with OpenAI. To the contrary, it is a hype and <i>vibe coding failure</i>.<p>But the AI bloggers will omit the vulnerability generation part.
The JFrog article is so sweaty...sort of "actually this is _good_ news". This whole mess points to the fundamental problem of running critical infrastructural services on open networks, and hoping that <your approach of choice to feeding/watering those services> keeps you safe. Just don't.
What they conveniently omit in the blog post is what the vulnerability was: it seems like they renewed JWTs without checking the signature at all ! You could write arbitrary info in an old token, and get it signed without any verification.<p><a href="https://www.youtube.com/watch?v=q2KCrmQz9WE" rel="nofollow">https://www.youtube.com/watch?v=q2KCrmQz9WE</a>
That video suggests that RTDEV-92030 was the fix for the issue - but <a href="https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases" rel="nofollow">https://docs.jfrog.com/releases/docs/artifactory-self-manage...</a> says that issue was resolved in a 15 July 2026 release of Artifactory, which doesn't fit our timeline - that was prior to the original Hugging Face post on 16 July which was several days before OpenAI had confessed.
I believe the technical term for that is "big oof"
There is one thing that is still unclear to me after reading a lot about the hack:<p>* were the ExploitGym solutions actually available somewhere inside huggingface's private datasets ?<p>* was the model really trying to extract the solutions ? or had some sub-agent drifted enough from the original context that it was not even trying to solve the initial challenge ? that would look much worse for OpenAI, PR-wise.
I thought the new trust model was to ask the frontier cybersecurity model to hack your code and generate CVEs and to find the vulnerabilities ahead of time and fix them before receiving reports about your users being exploited?<p>And in OpenAI's case to ask the model to try to find vulnerabilities and breakout before running training in the environment.<p>Fast remediation would be the new standard to outside vulnerability reports, but also a follow up to determine how you can adapt the approach of the reporter to find vulnerabilities preemptively.
So they are the proxy in the hugging face hacking incident?<p>Way to bury that lede.
This works if only 'trusted' actors have access to frontier class models that can search for vulnerabilities. With a near-frontier model available with open weights then attackers will be able to do plenty of damage even with 'fast remediation'