CVE-2026-55588 oras-project CVE debrief

Who should care

Defenders responsible for automation or CI/CD pipelines using ORAS against untrusted registry metadata should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify ORAS CLI version and upgrade to 1.3.3 if necessary, and implement compensating controls to monitor and limit resource usage.

Why it matters

A vulnerability in ORAS CLI versions up to 1.3.2 allows a malicious OCI registry to cause a client-side denial of service, affecting automation or CI/CD pipelines that use ORAS against untrusted registry metadata. Defenders should prioritize verifying ORAS CLI version and upgrading to 1.3.3 if necessary.

• Denial of service through CPU and memory exhaustion
• Potential disruption of automation or CI/CD pipelines
• Need for verification of ORAS CLI version and exposure

Technical summary

The vulnerability is caused by recursive referrer traversal not tracking visited descriptors, allowing a malicious OCI registry to create a cyclic referrer graph. This issue affects oras discover, backup, and restore workflows, and has been fixed in version 1.3.3. A cyclic graph can be as simple as A referring to B and B referring back to A, which can 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.

Defensive priority

Defenders should prioritize verifying ORAS CLI version and upgrading to 1.3.3 if necessary, and assess exposure in automation or CI/CD pipelines using ORAS against untrusted registry metadata.

Recommended defensive actions

• Verify ORAS CLI version and upgrade to 1.3.3 if necessary
• Assess exposure in automation or CI/CD pipelines using ORAS against untrusted registry metadata
• Implement compensating controls to monitor and limit resource usage
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The vulnerability is caused by recursive referrer traversal not tracking visited descriptors, allowing a malicious OCI registry to create a cyclic referrer graph. This issue has been fixed in version 1.3.3.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.