Two vulnerabilities in JFrog Artifactory have been identified that could enable anonymous or low-privileged users to manipulate package metadata without altering the underlying artifacts, potentially leading to software supply chain compromises. The flaws, reported by Oligo Security to JFrog on June 25 and publicly detailed on August 20, have since been patched by JFrog.
The first vulnerability, CVE-2026-69106, carries a CVSS score of 8.8 and relates to Artifactory's handling of the X-Orig-Client-Uri header. The second, CVE-2026-65922, has a CVSS score of 5.4 and permits writes into trusted .jfrog/ metadata paths. Both are listed in the National Vulnerability Database.
CVE-2026-69106 arises because Artifactory accepts the X-Orig-Client-Uri header from external clients without verifying its origin from trusted routing infrastructure. Oligo Security's researchers discovered that virtual repositories could exploit this to create a cross-user cache poisoning scenario. In Helm, the full attacker-controlled URL was written into generated metadata, but only its 32-bit Java hash was used for cache location. This allowed a different URL with the same hash to be constructed, potentially serving a poisoned index to subsequent users. While npm had a separate cache protection mechanism, it failed to check the X-Orig-Client-Uri header, only two other override headers.
A related issue was also found in JFrog's recommended nginx configuration. When a caching reverse proxy was deployed, the X-Forwarded-Proto header could be used to influence generated absolute URLs.
The second vulnerability, CVE-2026-65922, impacts how Artifactory handles internal .jfrog/ metadata. The REST COPY and MOVE APIs, as well as WebDAV MKCOL, could access these paths without the usual protections applied to standard uploads. This authorization path treated .jfrog/ as trusted, allowing an authenticated user with appropriate repository access to place or create content within these directories. Oligo Security noted that these files are consumed by package handlers for functions such as npm signing keys, OCI referrers, Docker indexes, and Ansible indexes.
To mitigate these risks, researchers recommend upgrading Artifactory to a patched release. They also advise disabling anonymous access where it is not strictly necessary, especially in shared or internet-accessible environments. Furthermore, organizations should review users and service accounts with repository access and consider stripping or overwriting client-supplied X-Orig-Client-Uri and X-Forwarded-Proto headers at the routing boundary.
