Skip to main content
VulnerabilityPublished

CVE-2026-44938: SUSE Rancher · Insufficiently Protected Credentials

Affects SUSE RancherSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High · fixed in 0.15.2 : patch SUSE Rancher soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.15.2, 0.14.6, 0.13.11 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Rancher and github.com/rancher/fleet to 0.15.2, 0.14.6, 0.13.11 or 0.12.15.

Affected software

ProductAffectedFixed in
SUSERancherAffected
  • >=0.15.0 <0.15.2
Fixed in
  • 0.15.2
SUSERancherAffected
  • >=0.14.0 <0.14.6
Fixed in
  • 0.14.6
SUSERancherAffected
  • >=0.13.0 <0.13.11
Fixed in
  • 0.13.11
SUSERancherAffected
  • >=0.12.0 <0.12.15
Fixed in
  • 0.12.15
GitHubgithub.com/rancher/fleetpkg:github/github.com/rancher/fleetOther threatsAffected
  • >=0.15.0 <0.15.2
  • >=0.14.0 <0.14.6
  • >=0.13.0 <0.13.11
  • >=0.12.0 <0.12.15
Fixed in
  • 0.15.2
  • 0.14.6
  • 0.13.11
  • 0.12.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict git push access to trusted users only and monitor repository changes for unauthorized modifications to namespaceLabels in fleet.yaml or BundleDeployment specifications.

Description

A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleDeployment.spec.options.namespaceLabels) when applying them to the target namespace. An attacker with git push access to a Fleet-monitored repository could overwrite Pod Security Standards (PSS) enforcement labels on a target namespace. This allows the attacker to weaken admission controls and deploy workloads that PSS policies would otherwise block.

References

Community reviews

Loading reviews…