A critical vulnerability identified as CVE-2026-82329 in JFrog Artifactory is being actively exploited by attackers to generate administrator tokens without authentication on self-managed deployments that use default configuration settings.
The flaw permits an unauthenticated attacker who has network access to the instance to issue or forge admin tokens, resulting in immediate administrative privileges. Once inside, the intruder can enumerate users, groups, and credential sets, inspect sensitive configurations, and gain visibility into federated topologies.
Attackers can also read stored artifacts and alter security settings. This combination is especially dangerous in organizations that rely on Artifactory as the central component of their software build and publication lifecycle.
The most damaging scenario occurs when the repository automatically supplies artifacts to CI/CD tools and deployment systems. By substituting a trusted internal package, container image, or dependency, an attacker can propagate malicious changes through build runners into production environments, creating a classic supply-chain compromise with a single point of entry affecting multiple downstream systems.
JFrog Cloud instances were already protected. For on-premises deployments, administrators must update to one of the following patched versions: 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, or 7.161.20. Applying the patch is insufficient if tokens have already been issued, because token validity, expiration, and revocation operate independently of the binary update.
Recommended actions include prioritizing internet-exposed instances, restricting network access, revoking and reissuing administrator tokens, reviewing token expiration policies, and rotating credentials linked to pipelines and systems that authenticate against the repository. Security teams should also examine audit logs for anomalous token creation, mass user and group enumeration, configuration changes, and unusual administrative API access.
Organizations that kept the service exposed during the vulnerable window should treat the environment as potentially compromised. This requires validating the integrity of all artifacts published during that period and checking for substitutions. Additional hardening measures include pinning images to immutable digests and verifying signatures and provenance at deployment time.
