CVE-2026-66384
KEVJFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory Vulnerability
Description
JFrog Artifactory contains an improper limitation of a pathname to a restricted directory vulnerability. This can allow an authenticated user to write data outside the intended Docker cache path under specific remote-repository conditions.
An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:NPublishedAug 12, 2026
Last modifiedOct 24, 2026
Added to KEVAug 27, 2026
Remediation dueSep 10, 2026
References
- docs.jfrog.com/releases/docs/artifactory-self-managed-releasesRelease NotesVendor Advisory
- docs.jfrog.com/releases/docs/jfrog-security-advisoriesVendor Advisory
- cdn.openai.com/pdf/67869394-cb91-4c12-888c-5cbd85c7814c/OpenAI-Hugging-Face%20Incident-Technical-Report.pdfTechnical Description
- openai.com/index/hugging-face-incident-and-the-road-ahead/Third Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-66384US Government Resource
0 recent articles mention this CVE
57
Risk assessment · Medium
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 46 days
- CVSS
- 5.3 MEDIUM
- EPSS (30-day exploit probability)
- 0.66% · top 48% of all CVEs
- Weakness
- CWE-22
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.