CVE Vulnerabilities

CVE-2026-35172

Improper Access Control

Published: Apr 06, 2026 | Modified: Jul 02, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

NameVendorStart VersionEnd Version
DistributionDistribution*3.1.0 (excluding)
Red Hat OpenShift Container Platform 4.12RedHatopenshift4/ose-operator-lifecycle-manager:1781122773*
Red Hat OpenShift Container Platform 4.13RedHatopenshift4/ose-operator-lifecycle-manager:1781123052*
Red Hat OpenShift Container Platform 4.14RedHatopenshift4/ose-operator-lifecycle-manager:1781833795*
Red Hat OpenShift Container Platform 4.15RedHatopenshift4/ose-operator-lifecycle-manager-rhel9:1779915499*
Red Hat OpenShift Container Platform 4.16RedHatopenshift4/ose-operator-lifecycle-manager-rhel9:1780957268*
Docker-registryUbuntuesm-apps/xenial*

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References