CVE-2026-66380: OCI Information Disclosure Vulnerability

CVE-2026-66380 Overview

CVE-2026-66380 is a missing authorization vulnerability [CWE-862] affecting JFrog Artifactory. An authenticated user without repository read permission may access private Open Container Initiative (OCI) referrer metadata under specific conditions. The flaw allows a low-privileged authenticated actor to enumerate metadata that should remain restricted to users with explicit read access on the target repository.

The issue affects confidentiality of OCI artifact referrer information. It does not permit modification of data or disruption of service. Exploitation requires network access to the Artifactory instance and valid, low-privileged credentials.

Critical Impact
Authenticated users without repository read rights can retrieve private OCI referrer metadata, exposing information about container artifacts stored in restricted repositories.

Affected Products

JFrog Artifactory Self-Managed (see vendor release notes for affected versions)
JFrog Artifactory Cloud (as remediated per vendor security advisories)
Deployments serving private OCI repositories with the referrers API enabled

Discovery Timeline

2026-08-12 - CVE-2026-66380 published to the National Vulnerability Database (NVD)
2026-08-12 - Last updated in NVD database

Technical Details for CVE-2026-66380

Vulnerability Analysis

The vulnerability resides in the authorization logic that governs access to OCI referrer metadata within JFrog Artifactory. Artifactory implements the OCI Distribution Specification, including the referrers API used to associate signatures, attestations, and Software Bill of Materials (SBOM) artifacts with container images.

Under specific conditions, the referrers endpoint fails to enforce the same repository read permission checks applied to standard OCI blob and manifest requests. An authenticated user with any valid session can query the endpoint and receive metadata describing artifacts stored in repositories they are not authorized to view.

The disclosed metadata may include artifact digests, media types, annotations, and relationships between manifests. This information can reveal internal build pipelines, signing practices, image lineage, and the presence of specific software components in restricted environments.

Root Cause

The root cause is a missing authorization check [CWE-862] on the OCI referrers metadata pathway. The endpoint validates that the caller is authenticated but does not consistently verify that the caller holds read permission on the target repository before returning referrer descriptors.

Attack Vector

An attacker requires only network reachability to the Artifactory API and a low-privileged authenticated account. The attacker issues an OCI referrers API request targeting a repository they cannot normally access. When the vulnerable condition is triggered, Artifactory returns referrer metadata for private artifacts. No user interaction is required, and attack complexity is low.

Refer to the JFrog Security Advisories Document for exact request patterns and preconditions.

Detection Methods for CVE-2026-66380

Indicators of Compromise

Requests to OCI referrers API paths (for example, /v2/<name>/referrers/<digest>) originating from accounts that lack repository read permission.
Access logs showing successful 200 OK responses to referrers queries against private repositories from unexpected user principals.
Bursts of enumeration-style requests iterating across repository names or manifest digests from a single authenticated session.

Detection Strategies

Correlate Artifactory access.log and request.log entries against the effective permission model to flag referrers responses served to users without matching repository read grants.
Baseline normal referrers API usage per user and alert on statistically anomalous query volume or breadth across repositories.
Ingest Artifactory audit and access logs into a centralized analytics pipeline to run cross-repository authorization anomaly rules.

Monitoring Recommendations

Enable verbose request logging on the Artifactory OCI endpoints and forward events to a SIEM for retention and correlation.
Monitor for new or unusual service accounts and API tokens querying referrers endpoints outside their documented scope.
Track upgrade status of all Artifactory nodes against the fixed versions listed in the JFrog release notes to identify unpatched instances.

How to Mitigate CVE-2026-66380

Immediate Actions Required

Upgrade JFrog Artifactory to the fixed version identified in the JFrog Artifactory Release Notes.
Review the JFrog security advisory to confirm which deployment models and versions are impacted in your environment.
Audit recent access to OCI referrers endpoints and identify any users who retrieved metadata for repositories outside their permission scope.

Patch Information

JFrog has published fixed builds through its standard release channel. Administrators should consult the JFrog Security Advisories Document for the specific version numbers that remediate CVE-2026-66380 and follow the documented upgrade procedure for self-managed installations. JFrog Cloud tenants receive vendor-managed updates.

Workarounds

Restrict authenticated API access to Artifactory using network segmentation and allowlists until patching is complete.
Rotate or disable low-privileged tokens and service accounts that are not actively required, reducing the pool of accounts that can reach the vulnerable endpoint.
Review repository permission targets and remove blanket authenticated-user grants that expand the attack surface for the referrers API.

bash

# Configuration example: verify Artifactory version after upgrade
curl -u <admin_user>:<admin_token> \
  -X GET https://<artifactory-host>/artifactory/api/system/version

# Example: list users with permission targets on a sensitive repo
curl -u <admin_user>:<admin_token> \
  -X GET https://<artifactory-host>/artifactory/api/security/permissions