Authenticated users may write data outside the intended Docker cache path (CVE-2026-66384)

What is affected, what to do

An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.

The vulnerability is being actively exploited; treat it as a priority. Update JFrog Artifactory to version 7.146.35, JFrog Artifactory to version 7.161.16. Immediate actions, mitigation and detection rules are in the runbook below.

Affected

• JFrog Artifactory lt *..7.146.35
• JFrog Artifactory lt 7.161.0..7.161.16

Fixed in

• JFrog Artifactory 7.146.35
• JFrog Artifactory 7.161.16

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

Response and mitigation

1. 01

   Runbook step 1

   Immediate response (0-24 h)

   • Patch self-managed instances: Upgrade Artifactory to the fixed build for your release line: 7.146.35 for the 7.146.x line, or 7.161.16 for the 7.161.x line (7.161.0 up to, but not including, 7.161.16 is affected). Record GET /artifactory/api/system/version before and after the upgrade, and confirm every node in an HA cluster.
   • SaaS tenants: Verify the instance runs 7.164.0 or later. If it does not, ask JFrog support to confirm the rollout and keep the evidence for your NIS2 records.
   • Inventory Docker remote repositories: List every docker remote repository (GET /artifactory/api/repositories?type=remote&packageType=docker). Until you patch, disable unused remotes or remove them from virtual repositories. Restrict upstream URLs to trusted registries such as Docker Hub or your internal registry.
   • Freeze privileges: Reduce repository-level "Manage"/"Admin" rights and the ability to create or modify remote repositories to the minimum. Revoke and reissue access tokens and API keys for accounts that hold deploy or cache rights on Docker remotes without a clear need.
   • Kick off an integrity check: The impact is integrity (writes outside the cache path), so look for unexpected, recently modified files under $JFROG_HOME/artifactory/var/ that sit outside the Docker cache and filestore layout (e.g. find $JFROG_HOME -newer <reference-file> -type f). Pay particular attention to config files (etc/, system.yaml) and plugin directories.
2. 02

   Runbook step 2

   Mitigation layers

   • IAM / least privilege: Disable anonymous access. Grant Docker remote repositories only to groups with a documented need. Limit CI/CD service accounts to read-only on remotes, and keep deploy/annotate rights on local repositories only.
   • Configuration hardening: Enable "Block Mismatching Mime Types" and tight include/exclude patterns on Docker remotes. Point remote URLs only at an approved allowlist of registries. Manage repository configuration through infrastructure-as-code with mandatory peer review.
   • Host hardening: Run Artifactory as the unprivileged artifactory user, never as root. In containers, mount configuration paths read-only and keep only data and filestore paths writable. Apply an SELinux/AppArmor profile that confines JVM writes to var/data, var/backup and the cache directory.
   • Network segmentation: Expose the UI and Docker endpoints (typically 443 via reverse proxy, 8081/8082 internally) only to build networks and developer VLANs. Do not expose the management UI directly to the internet. Route Artifactory egress through a proxy that permits only approved upstream registries.
   • Reverse proxy / WAF: At the fronting Nginx/HAProxy/WAF, deny requests to /v2/ and /artifactory/api/docker/ that contain traversal sequences (../, ..%2f, %2e%2e, %252e, ..\). ModSecurity idea: SecRule REQUEST_URI "@rx (?i)(\.\.|%2e%2e|%252e)(/|%2f|%5c)" "phase:1,deny,id:1066384,msg:'Artifactory Docker path traversal'".
   • Supply-chain guardrail: Enforce signature verification (Cosign/Notation) in deployment pipelines for images pulled from Artifactory, so tampered artefacts cannot reach production silently.
3. 03

   Runbook step 3

   Detection rules

   • Artifactory request log (var/log/artifactory-request.log) or proxy access log: look for authenticated Docker API calls that contain traversal patterns. SPL: index=artifactory sourcetype=artifactory:request uri="*/v2/*" (uri="*..*" OR uri="*%2e%2e*" OR uri="*%252e*") | stats count by user, remote_ip, uri
   • Linux auditd: Watch for writes by the Artifactory JVM outside the expected data paths. Rules: -w $JFROG_HOME/artifactory/var/etc -p wa -k artifactory_cfg and -a always,exit -F arch=b64 -S openat -F auid!=unset -F uid=artifactory -F dir=/opt -F success=1 -k art_write. Alert on hits outside var/data and var/work.
   • Configuration changes: Use the Artifactory access audit log (access-audit.log) or event webhooks to flag new or modified Docker remote repositories and changed remote URLs. Treat changes by accounts that do not normally perform admin actions as high priority.
   • EDR / process ancestry: Escalate any executable, script or Groovy plugin (etc/artifactory/plugins/*.groovy) newly written by the Artifactory Java process, and any child processes that follow (java → sh/bash).
   • Zeek/Suricata: Detect outbound connections from Artifactory to registry hosts that are not on the allowlist (HTTP /v2/ paths to unknown destinations). A deviation from the upstream allowlist may indicate a tampered remote repository configuration.

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2

NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

Read in glossary

Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).

CRA

The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

Read in glossary

Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.

ISO/IEC 27001

ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

Read in glossary

Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.

Source: NVD (NIST), pwn.watch, CISA KEV Catalog, cvelistv5, BSI WID Portal, BSI CSAF

Vendors and products

• JFrog JFrog Artifactory
• JFrog Artifactory Saas
• JFrog Artifactory Self-managed

Weakness classes (CWE)

• CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  Base

  The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

  Entry at MITRE CWE-22

References & sources

• docs.jfrog.comJFrog Artifactory — CVE-2026-66384Vendor advisory, Vendor advisory, pwn-watch
• docs.jfrog.comreleases/docs/artifactory-self-managed-releasesVendor advisory, Release notes, Vendor advisory
• cdn.openai.compdf/67869394-cb91-4c12-888c-5cbd85c7814c/OpenAI-Hugging-Face In…Third-party advisory, Technical description
• openai.comindex/hugging-face-incident-and-the-road-aheadThird-party advisory, Third-party advisory
• cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-66384government-resource, US government resource
• pwn.watchpwn.watch: JFrog Artifactory: JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory Vulnerabilitypwn-watch
• NVD (NIST)NVD: CVE-2026-66384pwn-watch
• cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

1. 28.08.2026NVD analysis modifiedNVD

   New references:

   • https://cdn.openai.com/pdf/67869394-cb91-4c12-888c-5cbd85c7814c/OpenAI-Hugging-Face%20Incident-Technical-Report.pdf
   • https://openai.com/index/hugging-face-incident-and-the-road-ahead/
   • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-66384
   Show 3 original changes

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   Reference type	added	—	CISA-ADP: https://cdn.openai.com/pdf/67869394-cb91-4c12-888c-5cbd85c7814c/OpenAI-Hugging-Face%20Incident-Technical-Report.pdf Types: Technical Description
   Reference type	added	—	CISA-ADP: https://openai.com/index/hugging-face-incident-and-the-road-ahead/ Types: Third Party Advisory
   Reference type	added	—	CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-66384 Types: US Government Resource

   Source identifier: nvd@nist.gov

2. 28.08.2026Record modifiedCISA ADP

   CISA assessment (SSVC): exploitation: active, automatable: no

   Show the original change

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   SSVC assessment	changed	{"id":"CVE-2026-66384","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-08-27T17:44:21.737733Z"}	{"id":"CVE-2026-66384","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-08-27T00:00:00+00:00"}

   Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

3. 27.08.2026Record modifiedjfrog.com

   New references:

   • https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases
   • https://docs.jfrog.com/releases/docs/jfrog-security-advisories
   Show 6 original changes

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   Reference	added	—	https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases
   Reference	added	—	https://docs.jfrog.com/releases/docs/jfrog-security-advisories
   Reference	removed	https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases	—
   Reference	removed	https://docs.jfrog.com/releases/docs/jfrog-security-advisories	—
   Reference type	removed	https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases Types: Release Notes, Vendor Advisory	—
   Reference type	removed	https://docs.jfrog.com/releases/docs/jfrog-security-advisories Types: Vendor Advisory	—

   Source identifier: reefs@jfrog.com

4. 27.08.2026Record modifiedCISA ADP

   CISA assessment (SSVC): exploitation: active, automatable: no

   New references:

   • https://cdn.openai.com/pdf/67869394-cb91-4c12-888c-5cbd85c7814c/OpenAI-Hugging-Face%20Incident-Technical-Report.pdf
   • https://openai.com/index/hugging-face-incident-and-the-road-ahead/
   • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-66384
   Show 4 original changes

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   Reference	added	—	https://cdn.openai.com/pdf/67869394-cb91-4c12-888c-5cbd85c7814c/OpenAI-Hugging-Face%20Incident-Technical-Report.pdf
   Reference	added	—	https://openai.com/index/hugging-face-incident-and-the-road-ahead/
   Reference	added	—	https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-66384
   SSVC assessment	changed	{"id":"CVE-2026-66384","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-08-12T18:42:06.743560Z"}	{"id":"CVE-2026-66384","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-08-27T17:44:21.737733Z"}

   Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

2 NVD translations into other languages are hidden.

Linked advisories

• CISA Adds 10 CVEs to Known Exploited Vulnerabilities Catalog, Five with Three-day Mitigation DeadlinesSANS NewsBites28.08.2026