<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T11:55:02.991524+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-48978</id>
    <title>CVE-2026-48978 — oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens</title>
    <updated>2026-10-12T11:55:02.994677+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> oras-project oras-go</p>
<p>oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, auth.Client follows the realm URL from a registry's WWW-Authenticate: Bearer challenge without validating the scheme or host, allowing a malicious or compromised registry to cause SSRF to internal networks such as http://169.254.169.254/, http://10.0.0.x/, and http://127.0.0.1/, or to downgrade a registry contacted over https:// to an http:// token endpoint in registry/remote/auth/client.go through Client.Do(), Client.fetchBearerToken(), fetchDistributionToken, and fetchOAuth2Token. This issue is fixed in version 2.6.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-48978"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vh4v-2xq2-g5cg</id>
    <title>GHSA-vh4v-2xq2-g5cg — ORAS Go forwards registry credentials across registry redirects</title>
    <updated>2026-10-12T11:55:02.994744+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: oras.land/oras-go/v2</p>
<p># ORAS Go forwards registry credentials across registry redirects</p>
<p>Reporter / public credit: JUNYI LIU</p>
<p>## Summary</p>
<p>ORAS Go can forward registry credentials configured for one registry origin to a different HTTP origin during registry redirects.</p>
<p>There are two related paths:</p>
<p>1. A manifest or metadata request authenticates to the origin registry, then the origin returns a redirect to another host or port. The redirected request can carry the origin `Authorization` header to the redirect target.
2. A blob upload `POST` authenticates to the origin registry, then the origin returns an upload `Location` on another host or port. The follow-up `PUT` can carry the origin `Authorization` header to the `Location` target.</p>
<p>The upload `Location` issue appears related to the existing public fix in pull request #1152 / GHSA-jxpm-75mh-9fp7. The manifest redirect path is a residual adjacent route: the v2 branch after the upload `Location` fix still forwards Basic credentials on an authenticated manifest redirect.</p>
<p>## Impact</p>
<p>A registry response can cause an ORAS Go or ORAS CLI client to send configured registry credentials to an unintended endpoint. In common workflows, those credentials may come from a registry config / Docker-style auth file rather than command-line flags.</p>
<p>This is a credential exposure across the registry-origin boundary. I am not claiming remote code execution, registry compromise, arbitrary token theft, or live third-party impact.</p>
<p>## Affected Versions Tested</p>
<p>- `oras…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vh4v-2xq2-g5cg"/>
  </entry>
</feed>
