Self-hosted JFrog Artifactory servers are under active attack after adversaries chained two authentication and token-handling flaws to gain administrator-level control, create persistence, and deploy backdoors. Because Artifactory often sits at the center of software build and release pipelines, this is not just another appliance-patching story: a compromised repository manager can become a launch point for tampering with packages, stealing secrets, or reaching deeper into CI/CD environments.

According to reporting on new findings from Wiz, attacks were observed between August 15 and September 8 against Artifactory instances that had not applied already available fixes. The chain involved CVE-2026-42018 and CVE-2026-42016. Each weakness is damaging on its own, but together they allowed an unauthenticated attacker to move from no login to administrator authority in a small number of steps.

What the attack chain does

The first issue, CVE-2026-42018, can cause Artifactory to return a token associated with the internal anonymous user even when anonymous access is disabled. That token is low privilege, but it gives the attacker a foothold inside Artifactory's token model.

The second issue, CVE-2026-42016, lets that low-privilege token be exchanged for a token with administrator scope. The core failure is that Artifactory validates who issued the token and whether it is signed correctly, but does not sufficiently enforce what the token should be allowed to do. In observed incidents, administrative activity could appear in logs under token:anonymous, making the activity easy to miss if defenders only look for suspicious named accounts.

Wiz reportedly saw cases where attackers went from the initial unauthenticated request to creating a new administrator account in under five minutes. After gaining administrator privileges, attackers created persistent admin users, installed malicious Groovy plugins, executed shell commands through plugin functionality, and deployed backdoors. Some activity included droppers that downloaded binaries to world-writable locations such as /tmp, as well as a custom Rust backdoor with command-and-control capability.

Why Artifactory compromise is high impact

Artifactory is commonly trusted by developers, build systems, deployment tools, and automated scanners. That trust gives attackers several attractive options after compromise. They may search configuration files for secrets, inspect repository content, create long-lived access tokens, add malicious plugins, or attempt to influence artifacts consumed by downstream pipelines.

Even if there is no evidence of package tampering, defenders should treat administrative compromise of a repository manager as a serious supply-chain event. Review what the instance could access, which build agents authenticated to it, which credentials were stored nearby, and whether any artifacts were published or modified during the suspected exposure window.

A third vulnerability expands the risk

The same incident reporting also highlights CVE-2026-82329, a separate critical authentication bypass rated 9.8 CVSS. Unlike the two-flaw chain, this issue can grant administrator privileges by itself when an attacker has network access to an affected instance. Public exploitation activity reportedly began shortly after disclosure, with large-scale scanning and exploitation attempts observed by Fastly.

CVE-2026-82329 affects newer Artifactory branches as well, which means organizations cannot assume they are safe simply because they are outside the exact version range for the two-token chain. Administrators should compare their deployed version against JFrog's current advisories for all three CVEs and prioritize internet-exposed systems first.

Immediate actions for defenders

Upgrade self-hosted Artifactory to a fixed release for your branch. JFrog cloud instances reportedly require no customer action, but self-managed deployments do. For CVE-2026-42018, fixed builds include 7.111.20, 7.117.27, 7.125.19, 7.133.28, and 7.146.8. For CVE-2026-42016, JFrog lists 7.133.11 as the fixed version. For CVE-2026-82329, fixed builds include 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, and 7.161.20.

If immediate upgrading is not possible for CVE-2026-82329, apply JFrog's documented workaround involving an additional random join key in system.yaml. That workaround should be considered temporary risk reduction, not a substitute for updating.

The most important operational lesson is that patching closes the door, but it does not clean the room. An update will not remove attacker-created administrator accounts, revoke tokens already minted, uninstall malicious plugins, rotate stolen join keys, or erase backdoors. Treat any exposed, vulnerable instance as potentially compromised until reviewed.

Hunt and recovery checklist

Start with identity and token review. Look for administrator accounts that were not created through normal change control, especially names resembling proof-of-concept handles, random svc_ or labadmin_ patterns, or service-like names created outside expected provisioning workflows. Investigate any administrative operations attributed to anonymous or low-privilege identities.

Next, review access tokens issued during the exposure period, especially since late August for environments potentially affected by CVE-2026-82329. Revoke suspicious or unnecessary tokens and consider broad token rotation where exposure is plausible.

Inspect the plugin framework carefully. Malicious Groovy plugins are especially concerning because they can provide code execution on the Artifactory host. Review plugin files, plugin execution logs, unexpected outbound HTTP requests, and shell command activity initiated by Artifactory processes.

Finally, rotate sensitive shared secrets. If attackers may have read Artifactory configuration, rotate the platform join key, repository credentials, CI/CD credentials, and any secrets stored in configuration files or environment variables. Review repository changes and artifact publication events during the suspected compromise window.

Bottom line

This campaign shows why repository managers need the same urgency as identity systems and production control planes. Keep Artifactory off the public internet where possible, restrict administrative endpoints, monitor token creation, alert on anonymous administrative behavior, and make repository-manager patching part of emergency response—not routine monthly maintenance.

Source: The Hacker News source