CVE-2026-82329: JFrog Artifactory, is it exploitable where you run it
Code called: openReached: openControl in front: openExploitation known: yesWalk it through the four questions
What the flaw is
The Access service in front of Artifactory builds a list of join keys it will trust when a node asks to register. It splits a configuration string on commas without dropping empty entries. On a default install that string is empty, so an empty key ends up on the trusted list (Fastly).
Because the empty key's signing secret is fixed and derived from nothing, anyone can forge a token that the service accepts as a valid join request. The unauthenticated join endpoint then returns an admin-scoped token. JFrog classes it as improper authentication (CWE-287); the CNA score is 9.8.
The attacker gains full control of the platform: users, repositories, configuration, stored credentials and the ability to publish or alter artifacts. Fastly and Wiz both describe the exploit as one unauthenticated request.
Are you exposed: each condition and how to check it
| Condition for exposure | How to check it on your system |
|---|---|
| self-hosted Artifactory (not JFrog Cloud) on a release below the first fixed build for its train | Run GET /artifactory/api/system/version against the instance (a valid user is enough, anonymous works if enabled) and read the version field. In the UI, the version shows in the footer or About page. Compare with the table; for example 7.146.25 and 7.161.19 are affected, 7.161.20 is fixed. JFrog Cloud was already fixed by JFrog; self-hosted means you run the service or container yourself. |
| the join key setting is still the default, with no additionalJoinKeys value, and the Access join endpoint /access/api/v1/registry/join answers requests from the attacker's network without credentials | On the node, open system.yaml and look under shared, security for an additionalJoinKeys entry; for containers and Helm, check the environment variable JF_SHARED_SECURITY_ADDITIONALJOINKEYS. JFrog's workaround is to add that setting, and Fastly says the empty configuration value on a default install is what lets the empty key in. Then, from an untrusted network position, confirm that /access/api/v1/registry/join answers through your reverse proxy or load balancer. Wiz and Fastly saw exploitation as a POST to that path; no credentials are needed. |
Affected and fixed versions
| Release train | Affected (JFrog) | First fixed |
|---|---|---|
| Before 7.111.4 (7.111.0 to 7.111.3, and older trains such as 7.104) | Not listed by JFrog or NVD as affected | No fixed build is named for this CVE |
| 7.111.x | 7.111.4 to 7.111.20 | 7.111.21 |
| 7.117.x | 7.117.0 to 7.117.27 | 7.117.28 |
| 7.125.x | 7.125.0 to 7.125.19 | 7.125.20 |
| 7.133.x | 7.133.0 to 7.133.28 | 7.133.29 |
| 7.146.x | 7.146.0 to 7.146.36 (JFrog's table); 7.146.37 is in neither JFrog column, and NVD treats everything below 7.146.38 as affected | 7.146.38 |
| 7.161.x | 7.161.0 to 7.161.19 | 7.161.20 |
| Trains not listed above (for example 7.141) | Not listed by JFrog or NVD as affected | No fixed build is named for this CVE |
If the fix cannot go in yet
- Upgrade to the fixed build for your train (table above). This is the vendor's most reliable known remediation. Cost: a service restart and upgrade testing.
- Workaround if you cannot upgrade quickly (JFrog): generate your own random hex join key with openssl rand -hex 16, add it as additionalJoinKeys under shared, security in system.yaml (or set JF_SHARED_SECURITY_ADDITIONALJOINKEYS in containers), keep your existing joinKey entry, then restart the Access service or the whole JPD. Your existing join key keeps working, so cluster operation is unaffected. Cost: a restart, and the new key must be kept as secret as the join key.
- Patching does not revoke tokens already issued. Rotate the platform join key and revoke access tokens issued since 28 Aug 2026 (Fastly). Cost: every CI job, deploy pipeline and integration that holds a revoked token gets HTTP 401 until it is given a new one, so list those clients first and schedule the change; the join key rotation also needs the Access service restart.
- Reduce exposure: restrict network access to Artifactory and the Access paths to trusted systems (Wiz). Fastly Next-Gen WAF customers can enable the vendor's CVE-2026-82329 virtual patch rule. Cost: a WAF rule is a compensating control only and does not remove the flaw.
What to look for
- Any POST to /access/api/v1/registry/join (also /join/router and /join/router?override=true) that returns HTTP 201 and carries a token whose key ID (kid) is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 (SHA-256 of an empty string) is high-confidence evidence of compromise (Fastly). The kid is in the header of the JWT in the POST body, so it shows only where request bodies are captured: a WAF, a reverse proxy with body logging, or a packet capture. Artifactory's request*.log files in its log directory record the method, path and status, so there look for POST requests to the join paths that returned 201 from addresses that are not your cluster nodes. A normal cluster peer signs with a real join key and shows a different kid. Wiz saw 200 or 201 with an admin-scoped token in the response. User-agent indicators are easy to change. Cluster nodes legitimately call the join endpoint, so compare each source address with your node list before treating a 201 without that kid as an attack.
- Fastly user-agent strings: jfrt/0/7.161.19, JFrog-Access/7.141.17, JFrogArtifactory/7.146.25. Sample high-volume sources (Fastly): 213.136.72[.]87, 89.117.49[.]147, 45.33.75[.]219, 23.92.20[.]11, 173.255.226[.]148, 195.154.157[.]234, 62.210.87[.]212, 45.79.190[.]169, 163.172.132[.]245.
- Follow-on calls to correlate (Wiz): GET /api/system/configuration, PUT /api/security/users/
with an admin flag in customData, token minting at /access/api/v1/tokens, reads of /access/api/v1/system/security/join_key, and enumeration of users, repositories and tokens. Attackers also attached their own SSH keys to the users they created. - Account names seen (Wiz): Nxploited_ plus 3 characters, labadmin_ plus hex, 0xTerror, svc_ plus 8 characters, and look-alike names such as jfrog-distribution, jfrog-insight and repo-service.
- Files: Groovy plugins in $JFROG_HOME/var/etc/artifactory/plugins/ (rce.groovy, cmd.groovy, jwtToken.groovy, uploadFile.groovy, JFrogImage.groovy, metrics.groovy, httpSession.groovy), exposed at /artifactory/api/plugins/execute/
. A broken plugin API, or requests to registry/join, api/plugins or systemUpload rejected with HTTP 400, can mean a filter called traceFilter, held in memory, is installed (Wiz). Upgrading leaves these plugins and filters in place. - Attackers may truncate request*.log files, so empty or missing request logs are themselves an indicator (Wiz). If Access signing keys (private.key) were read, reset the token certificate; a patch does not revoke forged tokens.
Exploited 4 days after disclosure: disclosed 28 Aug 2026, first exploitation reported 1 Sep 2026.
Exploitation reported so far
Fastly Security Research reported on 3 Sep 2026 that probing began on 31 Aug 2026, mostly from offensive-security vendors, and that mass scanning followed on 1 Sep 2026 when a public exploit appeared. Individual IPs sprayed thousands of hosts, and sources grew to nearly 1,400 addresses in a day. Fastly counted about 406,000 attempts on 2 Sep 2026.
Wiz Research confirmed successful exploitation between 1 and 8 Sep 2026 by several actors, each doing different things: configuration theft, new admin accounts, long-lived tokens, join key theft, attached SSH keys and Groovy plugins. CISA added it to KEV on 2 Sep 2026 with a due date of 5 Sep 2026, flagged for forensic triage; ransomware use is listed as unknown.
Why agent investigation settles it
The version and the default join-key configuration show whether the instance could be hit, but the fix does not evict an attacker who already minted tokens, created users or planted plugins. For an instance that was reachable while vulnerable the useful question is whether it was compromised, which needs log and file investigation against the join endpoint and plugins directory.
Related pages
Sources
- CVE-2026-82329: NVD record, read 19 Nov 2026
- CVE-2026-82329: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
- CVE-2026-82329: JFrog security advisories (vendor advisory, CVE-2026-82329 section and workaround), read 19 Nov 2026
- CVE-2026-82329: Fastly Security Research report, 3 Sep 2026, read 19 Nov 2026
- CVE-2026-82329: Wiz Research report on CVE-2026-42016, CVE-2026-42018 and CVE-2026-82329 (the canonical URL as Wiz publishes it), published 10 Sep 2026, corrected 11 Sep 2026, extended 17 Sep 2026, read 19 Nov 2026
- CVE-2026-82329: JFrog documentation: Get Artifactory Version API, read 19 Nov 2026
Last reviewed 19 Nov 2026.