Skip to content
Zero Day Playbook

The artifact repository and CI system playbook for the first 72 hours

  • 0 to 4 hours: 3 steps
  • 4 to 24 hours: 4 steps
  • 24 to 72 hours: 3 steps
  • Hours elapsed: the bar under the cells

Checklist to print

  1. 0 to 4 hours3 steps, due by hour 4
    1. 1

      Platform engineering, hand-off

      Copy the logs before touching anything. Collect request*.log from the Artifactory log directory, the reverse proxy or load balancer access log, and on GitLab the Workhorse, api_json, graphql_json and application_json logs. Compute a SHA-256 for each file and store the copies on a host that is not the server.

      Done at

    2. 2

      Platform engineering, hand-off

      Get the exact version of every self-hosted Artifactory node with GET /artifactory/api/system/version (the version field) and match it to the build list in the upgrade step below. For GitLab, run head -1 /opt/gitlab/version-manifest.txt on Omnibus, or docker exec <container> head -1 /opt/gitlab/version-manifest.txt. Include test, staging and edge instances. Artifactory Cloud and GitLab.com need no action: the vendors patched them.

      Done at

    3. 3

      Platform engineering, hand-off

      On each Artifactory node, open system.yaml and look under shared, security for additionalJoinKeys (containers and Helm: the variable JF_SHARED_SECURITY_ADDITIONALJOINKEYS). If it is empty you are in the default configuration CVE-2026-82329 needs. Apply JFrog's workaround while the upgrade is prepared: generate a key with openssl rand -hex 16, add it as additionalJoinKeys, keep the existing joinKey entry, restart the Access service or the whole platform deployment. Then block /access/ at the proxy from every network that is not a cluster peer or a trusted admin range.

      Done at

  2. 4 to 24 hours4 steps, due by hour 24
    1. 4

      Platform engineering, hand-off

      Pick one target build that closes all three Artifactory flaws at once. Wiz's list of builds that close CVE-2026-42018 and CVE-2026-82329 is 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38 or 7.161.20 or later, and JFrog's advisory names 7.133.11 as the only patched build for CVE-2026-42016 (affected: everything before it), so trains 7.111, 7.117 and 7.125 should go to 7.133.29 or later to be sure of closing all three. The per-train targets for the other two bugs are: 7.111 to 7.111.21, 7.117 to 7.117.28, 7.125 to 7.125.20, 7.133 to 7.133.29, 7.146 to 7.146.38 (not 7.146.37: NVD counts everything below 7.146.38 as affected), 7.161 to 7.161.20. Back up first, upgrade, then re-run the version call.

      Done at

    2. 5

      Security lead, hand-off

      Search the proxy and application logs back to 28 Aug 2026. High-confidence evidence of CVE-2026-82329 is a POST to /access/api/v1/registry/join (also /join/router and /join/router?override=true) that returned HTTP 201 with a token whose key ID is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, the SHA-256 of an empty string. If your logs do not record response bodies, list every 200 or 201 on those paths from an address that is not a cluster peer. For the CVE-2026-42018 chain, look for a 401 on the bare AWS token path followed by a 200 on a variant of it from the same client, then POST /access/api/v1/tokens, then requests whose actor is token:anonymous creating users.

      Done at

    3. 6

      Platform engineering, hand-off

      For GitLab, upgrade the self-managed instance to 19.2.8, 19.3.5 or 19.4.2 or later for CVE-2026-97229; 19.4.1 is not enough because its earlier fix was incomplete. Until then limit who can create accounts and personal access tokens (Admin, Settings, General, Sign-up restrictions). Check the Workhorse log for a 502 with 'badgateway: failed to receive response: EOF' on POST /api/v4/projects/:id/ci/lint or /api/graphql, with a large read_bytes value and a correlation_id missing from api_json.log and graphql_json.log. GitLab calls that the highest-confidence signal.

      Done at

    4. 7

      Security lead, hand-off

      Rotate what an unauthenticated administrator could have read. Replace the platform join key. Revoke every access token issued since 28 Aug 2026 on any node that was reachable while below its fixed build, then reissue credentials to the CI jobs that need them. If you find signs of entry, or Access private.key may have been read, reset the Access token certificate: it invalidates every token and needs a planned window, but a patch does not revoke forged tokens.

      Done at

  3. 24 to 72 hours3 steps, due by hour 72
    1. 8

      Security lead, hand-off

      Hunt for persistence the upgrade left in place. Users: list all users and compare with the identity provider; names seen in 2026 were Nxploited_ plus 3 characters, labadmin_ plus hex, 0xTerror, svc_ plus 8 characters, and look-alikes such as jfrog-distribution, jfrog-insight and repo-service; also check SSH keys attached to users. Files: ls -la $JFROG_HOME/var/etc/artifactory/plugins/ for rce.groovy, cmd.groovy, jwtToken.groovy, uploadFile.groovy, JFrogImage.groovy, metrics.groovy, httpSession.groovy; a payload at /tmp/.z with SHA1 513a907b69edffc3cb77a494da395178d21ef9bd; binaries in /dev/shm, /tmp and /var/tmp. If the plugin API is broken, or registry/join, api/plugins or systemUpload requests are rejected with HTTP 400, an in-memory filter named traceFilter may be installed: restart the service from a clean state.

      Done at

    2. 9

      Application owner, hand-off

      Find what changed in your repositories during the exposure window with an AQL query posted to /artifactory/api/search/aql, for example items.find({"repo":"<release-repo>","modified":{"$gt":"2026-08-28T00:00:00.000Z"}}).include("name","path","sha256","modified_by"), and flag every artifact whose modified_by is not your CI publishing identity. Rebuild the flagged artifacts and the three most widely pulled ones from source on a clean runner and compare SHA-256 values. Hold the next release until they match.

      Done at

    3. 10

      Security lead, hand-off

      Rotate the secrets CI holds for the repository: the CI/CD variables that publish to Artifactory, runner registration and authentication tokens, deploy keys and access tokens, and gitlab-secrets.json if there are signs of code execution on GitLab. Replace long-lived Artifactory tokens in CI with short-lived ones scoped to one repository. Hunt files owned by git in /tmp and unexpected child processes of Puma or Sidekiq.

      Done at

Artifactory and GitLab sit at the point where source becomes software. A flaw in either is rarely about the server itself. The attacker wants what the server can do: mint administrator tokens, read the platform join key and the Access signing keys, add users with SSH keys, drop Groovy user plugins that run commands, or replace an artifact that thousands of builds pull. The Artifactory flaws of 2026 were exploited in exactly that order: an unauthenticated request, an administrator token, a new admin account, then persistence. Wiz saw some actors go from first request to a new admin account in under five minutes.

Patching is the hard part, because the patch closes the door and leaves everything the attacker took. An upgrade does not revoke a token already issued, remove an admin user, delete a Groovy plugin or invalidate a stolen signing key. Release trains also differ: Artifactory has six supported trains in the 2026 advisories, and the fixed build for one train is not a fixed build for the next. The CI system adds a second problem. GitLab runners and CI variables hold the tokens that publish to the repository, so a CI compromise becomes a repository compromise even when the repository is patched.

When no fix exists yet

JFrog gave no workaround for CVE-2026-42016 or CVE-2026-42018, and GitLab gave none for CVE-2026-97229. The only controls then are exposure controls. Restrict the web and Access paths to trusted networks or a VPN; the cost is that remote developers, external consumers and CI outside the allowed path lose access. On GitLab, limit sign-ups and token creation, which narrows who can reach the flaw without removing it. For CVE-2026-82329 JFrog did publish a workaround (the additionalJoinKeys step), and Fastly Next-Gen WAF customers could enable a virtual patch, which is a compensating control and not a fix.

Take the service offline when three things are true together: the node is below its fixed build, it cannot be moved behind an allow-list within hours, and the logs show hits or are missing. CISA's entry for CVE-2026-82329 tells you to follow vendor mitigations and to discontinue use of the product if mitigations are unavailable. Offline costs failed builds and failed deploys, so before you cut it, check that CI can pull dependencies from a remote-repository cache or a read-only mirror. Give the decision to a named person, with the time recorded.

CVE-2026-82329 worked through, hour by hour

JFrog published the advisory for the Artifactory join-key bypass on 28 Aug 2026. On a default install the Access service accepted an empty string as the cluster join key, so an unauthenticated caller could obtain an administrator token. CVSS base score 9.8. The table follows one self-hosted instance from advisory to mass exploitation, using Fastly's daily counts and the CISA entry. Fastly and JFrog give dates and daily counts, not hours, so the table keeps days; Wiz's change log gives the only hour-level times.

WhenWhat happenedSource
28 Aug 2026, Day 0JFrog publishes the advisory with fixed builds 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38 and 7.161.20 and the additionalJoinKeys workaround. NVD publishes the record. Fastly sees no exploitation that day.source
29 and 30 Aug 2026, Day 1 and 2Fastly records only single-digit probes on each day.source
31 Aug 2026, Day 3About 75,000 attempts, of which roughly 73,000 came from offensive-security vendors and research services (nearly 98%). About 72 hours after the advisory.source
1 Sep 2026, Day 4A public exploit appears. Fastly counts just above 171,000 attempts. Wiz's observed successful exploitation runs from this day to 8 Sep 2026.source
2 Sep 2026, Day 5CISA adds the CVE to KEV with a due date of 5 Sep 2026 and forensic triage marked Yes. Fastly counts its peak, about 406,000 attempts.source
3 Sep 2026, Day 6Fastly publishes its analysis and a WAF virtual patch rule for its Next-Gen WAF customers.source
10 Sep 2026, Day 13Wiz publishes its report of successful exploitation: configuration theft, new admin accounts, long-lived tokens, join key theft, attached SSH keys and Groovy plugins. It corrects the HTTP method for this CVE and the fixed versions for CVE-2026-42018 at 15:00 UTC on 11 Sep 2026, and adds the Groovy plugin section at 19:00 UTC on 17 Sep 2026.source

The playbook's first four steps fit inside the 72 hours before the first large wave. Logs copied and the additionalJoinKeys workaround applied in the first 4 hours, on 28 Aug, closes the empty-key door about three days before the 75,000-attempt day and about four days before the public exploit. An instance upgraded to its train build by 31 Aug was patched before the first success in Wiz's observed window, which opens 1 Sep. An instance that waited for the KEV listing acted on 2 Sep, day 5, the day of the 406,000 peak (5.4 times the 31 Aug volume), and for it the 201 search, the token rotation and the plugin hunt in the later steps decided whether the instance was safe.

Sources

  1. JFrog security advisories, read 19 Nov 2026
  2. Fastly on CVE-2026-82329, read 19 Nov 2026
  3. Wiz Research on Artifactory CVE-2026-42018 and CVE-2026-42016, read 19 Nov 2026
  4. CISA KEV entry for CVE-2026-82329, read 19 Nov 2026
  5. CISA KEV entry for CVE-2026-97229, read 19 Nov 2026
  6. NVD record for CVE-2026-82329, read 19 Nov 2026
  7. NVD record for CVE-2026-42016, read 19 Nov 2026
  8. NVD record for CVE-2026-42018, read 19 Nov 2026
  9. GitLab patch release 19.4.2, read 19 Nov 2026
  10. JFrog documentation: Get Artifactory Version API, read 19 Nov 2026
  11. NVD record for CVE-2026-97229, read 19 Nov 2026

Last reviewed 19 Nov 2026.