https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 10:26:14 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-333252 EUVD-2026-333252 https://cve.radiocsirt.org/vuln/euvd-2026-333252 https://cve.radiocsirt.org/vuln/fkie_cve-2026-44936 <p>Missing filtering when the helmRepoURLRegex field isn&#39;t set on a GitRepo resource in SUSE Rancher Fleet&#39;s bundle reader in 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 and 0.12 before 0.12.15 forwards Helm authentication credentials (BasicAuth) to any URL specified in the helm.repo field of a fleet.yaml file, allowing attackers able to push to fleet monitored git repos to leak helm access credentials.</p> <p>Missing filtering when the helmRepoURLRegex field isn&#39;t set on a GitRepo resource in SUSE Rancher Fleet&#39;s bundle reader in 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 and 0.12 before 0.12.15 forwards Helm authentication credentials (BasicAuth) to any URL specified in the helm.repo field of a fleet.yaml file, allowing attackers able to push to fleet monitored git repos to leak helm access credentials.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-44936 https://cve.radiocsirt.org/vuln/ghsa-hx4v-cxpf-vh8m <p><strong>Affected:</strong> Go: github.com/rancher/fleet</p> <p>### Impact A vulnerability has been identified in Fleet when the `helmRepoURLRegex` field isn&#39;t set on a `GitRepo` resource. Fleet&#39;s bundle reader forwards Helm authentication credentials (`BasicAuth`) to any URL specified in the `helm.repo` field of a `fleet.yaml` file.</p> <p>An attacker with git push access to a Fleet-monitored repository can exploit this behavior by specifying a malicious URL in `helm.repo`. This causes the Fleet controller to send the configured Helm repository credentials to the attacker’s server.</p> <p>As a result, the attacker can capture the username and password that an administrator configured to access a private Helm chart repository. However, the response body from the attacker&#39;s server isn&#39;t included in the error message (this behavior was fixed in Fleet `v0.13.3` and later), which prevents additional internal data from leaking through the status condition.</p> <p>The final severity of this vulnerability depends on the specific permissions of the leaked credentials.</p> <p>Fleet recommends you to: 1. Review your system for potentially leaked credentials. 2. Replace any credentials that might be compromised.</p> <p>Please consult the associated [MITRE ATT&amp;CK - Technique - Stored Data Manipulation](https://attack.mitre.org/techniques/T1565/001/) and [MITRE ATT&amp;CK - Technique - Steal Application Access Token](https://attack.mitre.org/techniques/T1528/) for further information about this category of attack.</p> <p>### Patches To resolve this vulnerability, upgrade to a patched ver…</p> <p><strong>Affected:</strong> Go: github.com/rancher/fleet</p> <p>### Impact A vulnerability has been identified in Fleet when the `helmRepoURLRegex` field isn&#39;t set on a `GitRepo` resource. Fleet&#39;s bundle reader forwards Helm authentication credentials (`BasicAuth`) to any URL specified in the `helm.repo` field of a `fleet.yaml` file.</p> <p>An attacker with git push access to a Fleet-monitored repository can exploit this behavior by specifying a malicious URL in `helm.repo`. This causes the Fleet controller to send the configured Helm repository credentials to the attacker’s server.</p> <p>As a result, the attacker can capture the username and password that an administrator configured to access a private Helm chart repository. However, the response body from the attacker&#39;s server isn&#39;t included in the error message (this behavior was fixed in Fleet `v0.13.3` and later), which prevents additional internal data from leaking through the status condition.</p> <p>The final severity of this vulnerability depends on the specific permissions of the leaked credentials.</p> <p>Fleet recommends you to: 1. Review your system for potentially leaked credentials. 2. Replace any credentials that might be compromised.</p> <p>Please consult the associated [MITRE ATT&amp;CK - Technique - Stored Data Manipulation](https://attack.mitre.org/techniques/T1565/001/) and [MITRE ATT&amp;CK - Technique - Steal Application Access Token](https://attack.mitre.org/techniques/T1528/) for further information about this category of attack.</p> <p>### Patches To resolve this vulnerability, upgrade to a patched ver…</p> https://cve.radiocsirt.org/vuln/ghsa-hx4v-cxpf-vh8m https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1715 <p>Ein Angreifer kann mehrere Schwachstellen in Fleet ausnutzen, um Sicherheitsmechanismen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen oder Sicherheitskonfigurationen zu manipulieren.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Fleet ausnutzen, um Sicherheitsmechanismen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen oder Sicherheitskonfigurationen zu manipulieren.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1715