<?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-03T16:18:08.228488+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/bit-helm-2021-32690</id>
    <title>BIT-helm-2021-32690 — Repository credentials passed to alternate domain</title>
    <updated>2026-10-03T16:18:08.372670+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: helm</p>
<p>Helm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, one may look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-helm-2021-32690"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2022-avi-1069</id>
    <title>certfr-2022-avi-1069 — De multiples vulnérabilités ont été découvertes dans les produits IBM.
Certaines d'entre elles permettent à un attaquan…</title>
    <updated>2026-10-03T16:18:08.372743+00:00</updated>
    <content>certfr-2022-avi-1069</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2022-avi-1069"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2021-53929</id>
    <title>cnvd-2021-53929</title>
    <updated>2026-10-03T16:18:08.372764+00:00</updated>
    <content>cnvd-2021-53929</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2021-53929"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-28061</id>
    <title>EUVD-2026-28061</title>
    <updated>2026-10-03T16:18:08.372778+00:00</updated>
    <content>EUVD-2026-28061</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-28061"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-32690</id>
    <title>fkie_cve-2021-32690</title>
    <updated>2026-10-03T16:18:08.372789+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Helm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, one may look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-32690"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-56hp-xqp3-w2jf</id>
    <title>GHSA-56hp-xqp3-w2jf — Helm passes repository credentials to alternate domain</title>
    <updated>2026-10-03T16:18:08.372814+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: helm.sh/helm/v3</p>
<p>While working on the Helm source, a Helm core maintainer discovered a situation where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository.</p>
<p>### Impact</p>
<p>The `index.yaml` within a Helm chart repository contains a reference where to get the chart archive for each version of a chart. The reference can be relative to the `index.yaml` file or a URL to location. The URL can point to any domain and this is a feature leveraged by Helm users. For example, an `index.yaml` file can be hosted on GitHub pages while the chart archives are hosted as GitHub releases. These are on different domain names and the `index.yaml` file points to the other domain.</p>
<p>When a username and password were associated with a Helm repository the username and password were also passed on to other domains referenced in the `index.yaml` file. This occurred when Helm went to retrieve a specific chart archive on the other domain.</p>
<p>### Patches</p>
<p>This issue has been resolved in 3.6.1.</p>
<p>There is a slight behavior change to credential handling with regard to repositories. Usernames and passwords are only passed to the URL location of the Helm repository by default. The username and password are scoped to the scheme, host, and port of the Helm repository. To pass the username and password to other domains Helm may encounter when it goes to retrieve a chart, the new `--pass-credentials` flag can be used. This flag restores the old…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-56hp-xqp3-w2jf"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-32690</id>
    <title>gsd-2021-32690</title>
    <updated>2026-10-03T16:18:08.372856+00:00</updated>
    <content>gsd-2021-32690</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-32690"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2021-32690</id>
    <title>msrc_CVE-2021-32690 — Repository credentials passed to alternate domain</title>
    <updated>2026-10-03T16:18:08.372868+00:00</updated>
    <content>msrc_CVE-2021-32690</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2021-32690"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhea-2021:3139</id>
    <title>RHEA-2021:3139 — Red Hat Enhancement Advisory: Web Terminal 1.3 release</title>
    <updated>2026-10-03T16:18:08.372884+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>helm: information disclosure vulnerability</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhea-2021:3139"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2339</id>
    <title>WID-SEC-W-2022-2339 — IBM DB2: Mehrere Schwachstellen</title>
    <updated>2026-10-03T16:18:08.372900+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in  IBM DB2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität zu gefährden.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2339"/>
  </entry>
</feed>
