CVE-2026-66384: JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory Vulnerability
JFrog · Artifactory
Listed by CISA as exploited in the wild since 27 Aug 2026. Below: exploitation status, EPSS and every published CVSS, each with its source, then affected versions and references.
Build snapshot collected · KEV catalog 2026.10.02 · EPSS of 2 Oct 2026 · not a live feed: collected once, at build time
Description
as written by CISA (KEV catalog)
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
CISA KEV
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.
Affected products and versions
CVE record · JFROG
jfrog · artifactory
- affected: before 7.146.35
- affected: from 7.161.0 before 7.161.16
Status words (affected, unaffected, unknown) and version bounds are copied from the record. An upper bound such as “before 7.1.0” usually marks the first fixed version; confirm in the vendor advisory before planning an upgrade.
References
CISA KEV notes and CVE record
- https://docs.jfrog.com/releases/docs/jfrog-security-advisories
- https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-66384
EPSS over the last 30 days
See also: the full KEV catalog
Related entries
Other JFrog entries in KEV
Added in the same week (see the week)
- CVE-2023-49105ownCloud Improper Authentication Vulnerability
- CVE-2026-53362Linux Kernel Unspecified Vulnerability
- CVE-2021-23758Ajax.NET Professional Deserialization of Untrusted Data Vulnerability
- CVE-2015-3246Red Hat Libuser Race Condition Vulnerability
- CVE-2015-5287Red Hat Automatic Bug Reporting Tool Privilege Escalation Vulnerability
- CVE-2022-0995Linux Kernel Out-of-Bounds Write Vulnerability
Questions about CVE-2026-66384
Is CVE-2026-66384 being exploited?
Yes, according to CISA. CVE-2026-66384 was added to the Known Exploited Vulnerabilities catalog on 27 Aug 2026, which CISA does only with reliable evidence of exploitation in the wild. The catalog field for ransomware campaign use says "Unknown".
What is the deadline to remediate CVE-2026-66384?
CISA set 10 Sep 2026 as the due date for US Federal Civilian Executive Branch agencies. The date is binding only for those agencies; other organisations can read it as a measure of urgency.
What is the EPSS score of CVE-2026-66384?
0.66%, in the 50th percentile, in the FIRST EPSS model of 2 Oct 2026. It estimates the probability of exploitation activity in the following 30 days. For a CVE already in KEV the score is secondary: exploitation has been observed.
How severe is CVE-2026-66384?
jfrog.com rates it 5.3 MEDIUM (CVSS 3.1). These are the published assessments as of 3 Oct 2026; this site does not rescore.
Which product does CVE-2026-66384 affect?
JFrog Artifactory, as named in the CISA catalog. The affected versions listed in the CVE record are on this page; the vendor advisory in the references is the authority on fixed versions.
Related sections
- WatchlistWhat attackers started using this month, most urgent first.
- Exploited catalogEvery flaw CISA lists as used in real attacks (KEV), searchable.
- CVE lookupType one identifier: attack status, probability, severity, versions.
- Attack probabilityEPSS score for up to 100 identifiers at once.
- VendorsWhich vendors have the most exploited flaws.
- RSS and JSON feedsFollow new exploited flaws for the vendors you run.
- Sources and methodWhere each number comes from and how the order is decided.