CVE-2026-66384

Authenticated users may write data outside the intended Docker cache path

MEDIUM

5.3

CVSS Score

Published: August 12, 2026 at 03:14 PM UTC

Updated: October 24, 2026 at 04:10 PM UTC

1 product affected across 1 vendorArtifactory

Using artifactory by jfrog?

Get instant alerts when new vulnerabilities affect artifactory - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploitation

CISA KEV

Exploit prediction

EPSS 0.7%

SSVC

Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score0.7%

EPSS (Exploit Prediction Scoring System) estimates a 0.7% chance this CVE is exploited in the wild within the next 30 days — higher than 52% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

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.

Required Action

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.

Ransomware Use

Unknown

Added to KEV

Aug 27, 2026

Remediation Due

Sep 10, 2026

49 days overdue

Notes

https://docs.jfrog.com/releases/docs/jfrog-security-advisories

https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases

BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk

Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk