Attackers chain three JFrog Artifactory flaws to plant Rust backdoors inside Fortune 100 build pipelines

Attackers chained three vulnerabilities in JFrog Artifactory to seize administrative control of self-hosted instances, plant a Rust-based backdoor, and maintain persistent access — in a campaign that ran for 24 days and could have poisoned software build pipelines across thousands of enterprises. Wiz researchers, who disclosed the attack chain on September 11, warned that between 49% and 62% of publicly accessible Artifactory instances remain vulnerable to at least one of the three flaws.

JFrog Artifactory is the DevOps world’s most widely used artifact repository, sitting inside the build pipeline of 83% of Fortune 100 companies. A compromised Artifactory instance is not merely a breached server: it is a staging point from which attackers can poison software artifacts before they reach developer workstations and production systems.

How the attack chain works

The campaign exploited three CVEs in sequence. The first step, CVE-2026-42018, extracted a JSON Web Token belonging to an internal anonymous user — even on instances where anonymous access is explicitly disabled. The second step, CVE-2026-42016, used insufficient token validation to escalate those limited privileges to full administrator level.

On some instances, attackers skipped both steps entirely by using CVE-2026-82329, a standalone authentication bypass rated CVSS 9.8 that affects Artifactory’s default configuration across six release branches up to version 7.161. An unauthenticated attacker with network access can forge an administrator token directly, without needing any prior foothold. According to Wiz, attackers in some observed cases went from first contact to administrator account creation in under five minutes.

Once inside with admin privileges, the attackers installed malicious Groovy plugins — a native Artifactory extension mechanism — to execute arbitrary system commands. They then deployed a custom Rust-based backdoor with command-and-control capabilities, ensuring persistence that survived even if the original vulnerability was later patched on the instance.

The 24-day campaign

According to Wiz’s disclosure, the exploitation campaign ran from August 15 to September 8, 2026. The attackers created rogue administrator accounts with long-lived access tokens, giving them durable access to the repository contents, build secrets, and any artifacts stored on those instances. The Rust backdoor was designed to remain active even after patching, meaning organizations that patched without first auditing for compromise may still have active implants.

Who is affected and what to do

All self-hosted Artifactory deployments on versions prior to the patched releases are at risk. JFrog-hosted cloud instances are not affected. Organizations should upgrade to version 7.111.21 or later — the exact patched version varies by release branch — and immediately audit their instances for suspicious activity: unauthorized administrator account creation, rogue access tokens, installed Groovy plugins that were not deployed by their team, and unusual outbound network connections.

For organizations that ran vulnerable versions during August and September, Wiz recommends treating the instances as potentially compromised and rotating all credentials, tokens, and secrets stored in Artifactory regardless of whether direct evidence of intrusion is found. Given the speed of exploitation observed — under five minutes in some cases — window-of-exposure time is not a reliable indicator of whether an instance was targeted.

The supply chain risk

The severity of this disclosure goes beyond the server compromise itself. Artifactory sits between code repositories and production deployments. An attacker with admin access can replace legitimate build artifacts — compiled libraries, container images, or packages — with malicious versions, allowing malware to flow downstream into every application built from that repository. This is the same attack surface exploited in the SolarWinds and 3CX supply chain compromises, applied to an infrastructure component that is nearly universal in enterprise DevOps pipelines.

Security teams running self-hosted Artifactory should treat this as an emergency, not a routine patch. Patch, audit for compromise indicators, rotate all secrets, and scan downstream artifacts for signs of tampering.