A critical authentication bypass vulnerability (CVE-2026-82329) in JFrog Artifactory is being exploited in attacks to create tokens that provide administrative access.
The flaw is present in the default configuration of self-managed instances of JFrog Artifactory, a repository manager used to store, organize, secure, and distribute software packages.
An unauthenticated attacker with network access could exploit it to gain administrative permissions.
Researchers at offensive security company watchTowr observed the flaw being exploited by “attackers minting themselves admin tokens.”
.png)
Details about the flaw are scarce, and JFrog’s advisory does not share many details beyond that the flaw is exploitable in Artifactory’s default configuration.
Vercel CEO Guillermo Rauch warned that the flaw’s impact could extend beyond compromising Artifactory itself.
“Administrative access to Artifactory reaches released artifacts that downstream systems already trust and pull automatically,” Collin Hogue-Spears, Senior Director of Solution Management at application security company Black Duck, told BleepingComputer.
Spears also notes that JFrog treats access tokens as independent credentials with their own expiration and revocation mechanisms, so upgrading the Artifactory binary does not by itself invalidate an already-issued token.
Because organizations use Artifactory to store binaries and packages consumed by build and deployment systems, attackers with administrative access could replace trusted artifacts and potentially execute malicious code on downstream systems.
Rauch also speculated that the vulnerability might be connected to recent research involving autonomous AI agents.
JFrog addressed the issue on August 28 in Artifactory versions 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, and 7.161.20. The vendor says that JFrog Cloud environments were already protected.
An attacker forging their own admin tokens means they can perform various sensitive actions, such as enumerating users, groups, and federated topologies, reading artifacts, changing security configurations, and poisoning existing packages.
However, the extent of the compromise, and whether servers were actually breached, is unclear. Victim counts, telemetry details, and indicators of compromise (IoCs) are also unclear.
BleepingComputer has contacted JFrog to confirm the reported activity, but we have not received a response yet.
Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply.
The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments.
Get the report
