A critical vulnerability tracked as CVE-2026-82329 in JFrog Artifactory is being actively exploited by attackers to issue administrator tokens without any authentication on self-managed installations that use default settings.
The flaw allows an unauthenticated attacker with network access to the instance to bypass authentication entirely and obtain full administrative privileges. From this position 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 particularly 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 pipelines. By replacing an internal package, container image, or dependency that the organization trusts, the attacker can propagate the change downstream from integration runners all the way to production environments, creating a classic supply-chain compromise with a single point of entry affecting multiple systems.
JFrog Cloud was already protected against the issue. Self-managed deployments must be updated to one of the following patched versions depending on the release branch: 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, or 7.161.20.
Applying the patch alone is insufficient if tokens have already been issued, because token validity, expiration, and revocation function independently of the binary update. Recommended actions include prioritizing internet-exposed instances, restricting network access, revoking and reissuing administrator tokens, reviewing expiration policies, and rotating credentials tied to pipelines and systems that authenticate against the repository.
Security teams should examine audit logs for anomalous token generation, mass user and group enumeration, configuration changes, and unusual administrative API access. Environments that remained exposed during the vulnerable window should be treated as potentially compromised, which includes validating the integrity of all artifacts published in that period and checking for unauthorized substitutions.
Additional hardening measures involve pinning images to immutable digests and verifying signatures and provenance at deployment time. Investigations should also extend to connected systems such as CI runners, deployment managers, and production servers to rule out persistence or malicious modifications.
