CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

JFrog Artifactory: authenticated Docker-cache path traversal (CVE-2026-66384) added to CISA KEV, a CI/CD artifact-store write primitive with no published exploitation narrative

cve · CVE-2026-66384

Coverage
1
first 2026-08-28 → last 2026-08-28
Latest activity
2026-08-28
A Medium-severity Artifactory write bug just became a confirmed-exploited CI/CD supply-chain concern via KEV…
Peak priority
notable
1 notable
Targets
public-sector
sectors: public-sector, technology
Sources cited
2
2 hosts

Action items (1)

Do-now tasks recorded on the entries about CVE-2026-66384, newest first. Check the date before acting on an older one.

  • Upgrade self-hosted JFrog Artifactory to 7.146.35 or 7.161.16 or later; CISA's KEV addition confirms active exploitation regardless of the Medium CVSS score, and Artifactory's role as a CI/CD artifact repository makes an out-of-scope write primitive a software-supply-chain concern for any downstream build or deployment that consumes its cache.
    2026-08-28CVE-2026-66384

Defender insights

What each entry about CVE-2026-66384 tells a defender to do, newest first.

Story timeline

  1. 2026-08-28JFrog Artifactory: authenticated Docker-cache path traversal (CVE-2026-66384) added to CISA KEV, a CI/CD artifact-store write primitive with no published exploitation narrative
    trending-vulnerabilitiesA Medium-severity Artifactory write bug just became a confirmed-exploited CI/CD supply-chain concern via KEV listing alone
ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessSupply Chain Compromise: Compromise Software Supply Chain

Initial Access TA0001

T1195.002Supply Chain Compromise: Compromise Software Supply Chain×1

Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise. Supply chain compromise of software can take place in a number of ways, including manipulation of the application source code, manipulation of the update/distribution mechanism for that software, or replacing compiled releases with a modified version.

Evidence: 2026-08-28/cve-2026-66384-jfrog-artifactory-docker-cache-traversal-kev · ATT&CK page ↗

Entries about JFrog Artifactory: authenticated Docker-cache path traversal (CVE-2026-66384) added to CISA KEV, a CI/CD artifact-store write primitive with no published exploitation narrative (1)

2026-08-28 · view entry permalink →

NOTABLECVE-2026-66384exploitedNATOA2

JFrog Artifactory: authenticated Docker-cache path traversal (CVE-2026-66384) added to CISA KEV, a CI/CD artifact-store write primitive with no published exploitation narrative

CISA added CVE-2026-66384 to its Known Exploited Vulnerabilities catalog on 2026-08-27. Per JFrog's own advisory, published 2026-08-12 with a CVSS 3.1 base score of 5.3 Medium (CWE-22, Improper Limitation of a Pathname to a Restricted Directory): "an authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions" (JFrog Security Advisories, 2026-08-12) in Artifactory self-hosted below 7.146.35 and 7.161.0 through 7.161.16. Fixed in 7.146.35 and 7.161.16; JFrog states cloud environments were already remediated with no customer action required.

Neither JFrog's advisory nor CISA's KEV entry describes the exploitation activity that justified the addition; the listing itself is the only exploitation evidence. Given Artifactory's role as a binary/artifact repository inside CI/CD release pipelines, a write primitive that escapes the intended cache path is a software-supply-chain concern despite the Medium base score and authentication requirement: an attacker able to plant or overwrite files outside the sandboxed cache location could influence what a downstream build or deployment consumes.

Triage: no exploitation mechanism has been described publicly, so there is no honest benign-lookalike discriminator to offer. The durable step is the upgrade itself and, where the environment allows it, reviewing Docker-cache directory contents for files outside their expected repository paths as a general compromise-assessment measure.

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

JFrog (Security Advisories) 2026-08-12
vulnerability28 Aug 05:50Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • cisa.gov1 (50%)
  • docs.jfrog.com1 (50%)