<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 18:33:28 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55588</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55588</link>
      <description>&lt;p&gt;ORAS (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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ORAS (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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55588</guid>
    </item>
    <item>
      <title>GHSA-298f-872v-2rcx — ORAS CLI: Cyclic Referrer Graph Can Cause Unbounded Recursion and Resource Consumption</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-298f-872v-2rcx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: oras.land/oras&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A malicious OCI registry can return a **cyclic referrer graph** (e.g. `A -&amp;gt; A` or `A -&amp;gt; B -&amp;gt; A`). The ORAS CLI&amp;#39;s recursive referrer traversal does not track visited descriptors, so a cycle causes unbounded recursion and memory growth — a client-side denial of service.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&amp;gt; **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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `oras discover`, recursive referrer traversal follows discovered referrers without maintaining a visited-descriptor set.&lt;/p&gt;
&lt;p&gt;Simplified flow:&lt;/p&gt;
&lt;p&gt;```text
runDiscover
  -&amp;gt; fetchAllReferrers(root)
     -&amp;gt; registry.Referrers(root)
     -&amp;gt; for each referrer:
          fetchAllReferrers(referrer)
```&lt;/p&gt;
&lt;p&gt;A malicious registry can create cyclic graphs such as:&lt;/p&gt;
&lt;p&gt;```text
A -&amp;gt; A
```&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;```text
A -&amp;gt; B -&amp;gt; A
```&lt;/p&gt;
&lt;p&gt;Because traversal does not track previously visited descriptors, recursion never reaches a terminating condition.&lt;/p&gt;
&lt;p&gt;Similarly, the recursive counting logic (`graph.RecursiveFindReferrers`, used by the `backup` and `restore` workflows) accumulates descriptors without cycle detection, causing unbounded memory growth.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: oras.land/oras&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A malicious OCI registry can return a **cyclic referrer graph** (e.g. `A -&amp;gt; A` or `A -&amp;gt; B -&amp;gt; A`). The ORAS CLI&amp;#39;s recursive referrer traversal does not track visited descriptors, so a cycle causes unbounded recursion and memory growth — a client-side denial of service.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&amp;gt; **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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `oras discover`, recursive referrer traversal follows discovered referrers without maintaining a visited-descriptor set.&lt;/p&gt;
&lt;p&gt;Simplified flow:&lt;/p&gt;
&lt;p&gt;```text
runDiscover
  -&amp;gt; fetchAllReferrers(root)
     -&amp;gt; registry.Referrers(root)
     -&amp;gt; for each referrer:
          fetchAllReferrers(referrer)
```&lt;/p&gt;
&lt;p&gt;A malicious registry can create cyclic graphs such as:&lt;/p&gt;
&lt;p&gt;```text
A -&amp;gt; A
```&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;```text
A -&amp;gt; B -&amp;gt; A
```&lt;/p&gt;
&lt;p&gt;Because traversal does not track previously visited descriptors, recursion never reaches a terminating condition.&lt;/p&gt;
&lt;p&gt;Similarly, the recursive counting logic (`graph.RecursiveFindReferrers`, used by the `backup` and `restore` workflows) accumulates descriptors without cycle detection, causing unbounded memory growth.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-298f-872v-2rcx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-55588</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-55588</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:26.04:LTS: oras&lt;/p&gt;
&lt;p&gt;ORAS (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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:26.04:LTS: oras&lt;/p&gt;
&lt;p&gt;ORAS (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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-55588</guid>
    </item>
  </channel>
</rss>
