Is CVE-2026-44936 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44936 being exploited in the wild.

How severe is CVE-2026-44936?

Medium severity, with a CVSS score of 5, published 6 July 2026.

Which products and versions are affected?

github.com/rancher/fleet (Go) SEMVER:introduced=0.12.0,fixed=0.12.15,introduced=0.13.0,fixed=0.13.11,introduced=0.14.0,fixed=0.14.6,introduced=0.15.0,fixed=0.15.2, SEMVER:introduced=0.15.0,fixed=0.15.2; Suse Fleet >= 0.15.0, = 0.14.0, = 0.13.0, = 0.12.0, < 0.12.15, 0.15.0 before 0.15.2, 0.14.0 before 0.14.6, 0.13.0 before 0.13.11, 0.12.0 before 0.12.15.

Is there a fix for CVE-2026-44936?

Yes. github.com/rancher/fleet (Go): upgrade to 0.15.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44936 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44936?

Check whether you run github.com/rancher/fleet (Go) or Suse Fleet at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44936: SUSE Rancher Fleet credential leak via unvalidated Helm repository URL

Q: Is there a fix for CVE-2026-44936?

Yes. github.com/rancher/fleet (Go): upgrade to 0.15.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44936 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-44936?

Check whether you run github.com/rancher/fleet (Go) or Suse Fleet at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44936 · Severity: medium · CVSS 5 · Published 2026-07-06

SUSE Rancher Fleet, a tool used to manage large-scale Kubernetes deployments, contains a security flaw that can lead to the theft of credentials. If an attacker has the ability to push code to a Git repository monitored by Fleet, they can trick the system into sending private Helm repository login details to a server they control. This could allow an attacker to gain unauthorized access to private software packages and internal application charts.

Technologies: github.com/rancher/fleet (Go), Suse Fleet. Vendors: Go, Suse.

Quick answers

Is CVE-2026-44936 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44936 being exploited in the wild.
How severe is CVE-2026-44936?: Medium severity, with a CVSS score of 5, published 6 July 2026.
Which products and versions are affected?: github.com/rancher/fleet (Go) SEMVER:introduced=0.12.0,fixed=0.12.15,introduced=0.13.0,fixed=0.13.11,introduced=0.14.0,fixed=0.14.6,introduced=0.15.0,fixed=0.15.2, SEMVER:introduced=0.15.0,fixed=0.15.2; Suse Fleet >= 0.15.0, < 0.15.2; >= 0.14.0, < 0.14.6; >= 0.13.0, < 0.13.11; >= 0.12.0, < 0.12.15, 0.15.0 before 0.15.2, 0.14.0 before 0.14.6, 0.13.0 before 0.13.11, 0.12.0 before 0.12.15.
Is there a fix for CVE-2026-44936?: Yes. github.com/rancher/fleet (Go): upgrade to 0.15.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44936 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44936?: Check whether you run github.com/rancher/fleet (Go) or Suse Fleet at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rancher/fleet (Go): upgrade to 0.15.2 or later
```
go get github.com/rancher/fleet@v0.15.2
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in the SUSE Rancher Fleet bundle reader. When a GitRepo resource is configured with a Helm secret but lacks the 'helmRepoURLRegex' field, the Fleet controller will forward BasicAuth credentials to any URL specified in the 'helm.repo' field of a fleet.yaml file. An attacker with 'git push' access to a monitored repository can modify the fleet.yaml to point to a malicious server, capturing the username and password used for Helm chart authentication. Patched versions (0.15.2, 0.14.6, 0.13.11, 0.12.15) now require an explicit 'helmRepoURLRegex' to be set before credentials will be forwarded.

Affected products

SUSE Rancher Fleet 0.15.0 before 0.15.2, 0.14.0 before 0.14.6, 0.13.0 before 0.13.11, 0.12.0 before 0.12.15

Identifiers

CVE-2026-44936
GHSA-hx4v-cxpf-vh8m
GO-2026-5873

Timeline

2026-05-27: disclosed: Initial disclosure in rancher/fleet repository
2026-07-01: advisory: GitHub Advisory published/reviewed
2026-07-06: advisory: NVD publication date

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.