ORAS CLI: Cyclic Referrer Graph Can Cause Unbounded Recursion and Resource Consumption
cve-program · CVE-2026-55588
PublishedORAS (OCI Registry As Storage) is a CLI and library for managing artifacts in OCI registries. In ORAS CLI versions up to and including 1.3.2, the recursive referrer traversal does not track visited descriptors, so a malicious OCI registry that returns a cyclic referrer graph causes unbounded recursion and memory growth. This affects oras discover, whose recursive traversal is enabled by default because the --depth option defaults to 0 (unlimited), as well as the recursive referrer counting used by the oras backup and oras restore workflows. A cyclic graph can be as simple as A referring to B and B referring back to A. A malicious registry can use this to cause a client-side denial of service, exhausting CPU and memory and hanging automation or CI/CD pipelines that run ORAS against untrusted registry metadata. The vulnerability does not extend to code execution, artifact substitution, or integrity bypass. This issue has been fixed in version 1.3.3.
Read the publisher's advisoryeuvd · EUVD-2026-66110
PublishedORAS (OCI Registry As Storage) is a CLI and library for managing artifacts in OCI registries. In ORAS CLI versions up to and including 1.3.2, the recursive referrer traversal does not track visited descriptors, so a malicious OCI registry that returns a cyclic referrer graph causes unbounded recursion and memory growth. This affects oras discover, whose recursive traversal is enabled by default because the --depth option defaults to 0 (unlimited), as well as the recursive referrer counting used by the oras backup and oras restore workflows. A cyclic graph can be as simple as A referring to B and B referring back to A. A malicious registry can use this to cause a client-side denial of service, exhausting CPU and memory and hanging automation or CI/CD pipelines that run ORAS against untrusted registry metadata. The vulnerability does not extend to code execution, artifact substitution, or integrity bypass. This issue has been fixed in version 1.3.3.
Read the publisher's advisorynvd · CVE-2026-55588
PublishedORAS (OCI Registry As Storage) is a CLI and library for managing artifacts in OCI registries. In ORAS CLI versions up to and including 1.3.2, the recursive referrer traversal does not track visited descriptors, so a malicious OCI registry that returns a cyclic referrer graph causes unbounded recursion and memory growth. This affects oras discover, whose recursive traversal is enabled by default because the --depth option defaults to 0 (unlimited), as well as the recursive referrer counting used by the oras backup and oras restore workflows. A cyclic graph can be as simple as A referring to B and B referring back to A. A malicious registry can use this to cause a client-side denial of service, exhausting CPU and memory and hanging automation or CI/CD pipelines that run ORAS against untrusted registry metadata. The vulnerability does not extend to code execution, artifact substitution, or integrity bypass. This issue has been fixed in version 1.3.3.
Read the publisher's advisoryosv · GHSA-298f-872v-2rcx
Published### Summary A malicious OCI registry can return a **cyclic referrer graph** (e.g. `A -> A` or `A -> B -> A`). The ORAS CLI's recursive referrer traversal does not track visited descriptors, so a cycle causes unbounded recursion and memory growth — a client-side denial of service. This affects `oras discover` (recursive referrer traversal) and the recursive referrer counting used by `oras backup` and `oras restore`. Because `oras discover --depth` defaults to `0` (unlimited), `discover` is affected out of the box. > **Note:** This advisory covers only the **ORAS CLI** (`oras.land/oras`). The related Referrers API pagination loop in the `oras-go` library is tracked in a separate advisory on the [oras-go](https://github.com/oras-project/oras-go) repository. ### Details In `oras discover`, recursive referrer traversal follows discovered referrers without maintaining a visited-descriptor set. Simplified flow: ```text runDiscover -> fetchAllReferrers(root) -> registry.Referrers(root) -> for each referrer: fetchAllReferrers(referrer) ``` A malicious registry can create cyclic graphs such as: ```text A -> A ``` or ```text A -> B -> A ``` Because traversal does not track previously visited descriptors, recursion never reaches a terminating condition. Similarly, the recursive counting logic (`graph.RecursiveFindReferrers`, used by the `backup` and `restore` workflows) accumulates descriptors without cycle detection, causing unbounded memory growth. ### PoC Create valid descriptors where: ```text referrers(A) = [A] ``` or: ```text referrers(A) = [B] referrers(B) = [A] ``` Run: ```bash oras discover attacker.local/repo@sha256:<A> ``` The recursive traversal continues indefinitely, causing unbounded recursion and eventual resource exhaustion. ### Impact A malicious OCI registry can trigger client-side denial of service against ORAS CLI users and automation. Potential impacts include: - Excessive CPU utilization - Excessive memory consumption - Unbounded recursion - Hung CI/CD jobs - Stalled automation pipelines - Failed backup or discovery operations The issue does not enable arbitrary code execution, artifact substitution, or integrity bypass, but it can reliably prevent ORAS operations from completing when interacting with malicious registry metadata. ### Patch - `cmd/oras/root/discover.go` — `fetchAllReferrers` threads a `visited` digest set; an already-traversed descriptor returns immediately, breaking cycles. Behavior is unchanged for valid (acyclic) referrer graphs. - `internal/graph/graph.go` — `RecursiveFindReferrers` tracks visited descriptors by digest and only recurses into unseen referrers, so traversal terminates on a cyclic graph.
Read the publisher's advisoryosv · GO-2026-6317
PublishedORAS CLI: Cyclic Referrer Graph Can Cause Unbounded Recursion and Resource Consumption in oras.land/oras
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-55588 · CVE overview and exploitation status
cve-program · CVE-2026-55588
- https://github.com/oras-project/oras/security/advisories/GHSA-298f-872v-2rcx
- https://github.com/oras-project/oras/commit/440eb65d07a0631f131944d28e7c29d562ec17f3
euvd · EUVD-2026-66110
- https://github.com/oras-project/oras/security/advisories/GHSA-298f-872v-2rcx
- https://github.com/oras-project/oras/commit/440eb65d07a0631f131944d28e7c29d562ec17f3
nvd · CVE-2026-55588
- https://github.com/oras-project/oras/commit/440eb65d07a0631f131944d28e7c29d562ec17f3
- https://github.com/oras-project/oras/security/advisories/GHSA-298f-872v-2rcx
osv · GHSA-298f-872v-2rcx
- https://github.com/oras-project/oras/security/advisories/GHSA-298f-872v-2rcx
- https://nvd.nist.gov/vuln/detail/CVE-2026-55588
- https://github.com/oras-project/oras/commit/440eb65d07a0631f131944d28e7c29d562ec17f3
- https://github.com/oras-project/oras
osv · GO-2026-6317
Related changes
Linked by CVE identifierNo related changes are available here.