dbcve.org
Rancher FleetApplication · Suse

CVE-2026-44937

HIGH · 8.2 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 0.12.15 / 0.13.11 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Potential forgery of webhook requests when using a unauthenticated webhook in SUSE Rancher Fleet 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 and 0.12 before 0.12.5 could be used by remote attackers to cause a denial of service or a downgrade attack on other repositories on the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SUSE Rancher Fleet contains a webhook authentication vulnerability where unauthenticated webhooks can be forged by remote attackers. This allows attackers to send crafted webhook requests that can cause denial of service or perform downgrade attacks on other repositories in the fleet.

MitigationUpgrade to patched versions (0.15.2, 0.14.6, 0.13.11, 0.12.5 or later). Until patched, review and restrict webhook configurations to require authentication or limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rancher FleetApplication
Affected:>= 0.12.0, < 0.12.15>= 0.13.0, < 0.13.11>= 0.14.0, < 0.14.6>= 0.15.0, < 0.15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Fleet version
    Query the Fleet deployment or Helm release to retrieve the running version. Common commands include `helm list -n fleet-system` or checking the deployment manifests for the fleet-agent or fleet-controller images.
    Affected if The installed version falls within any of the affected ranges: 0.12.0-0.12.14, 0.13.0-0.13.10, 0.14.0-0.14.5, or 0.15.0-0.15.1.
  2. Confirm webhook endpoints are exposed
    Review the Fleet service configuration to determine if webhook endpoints are accessible externally. Check ingress or route configurations in the fleet-system namespace for webhook-related endpoints.
    Affected if Webhook endpoints are exposed and reachable from untrusted networks.
  3. Inspect webhook authentication settings
    Examine the Fleet webhook configuration or CRD definitions to verify whether authentication and validation are enforced on incoming webhook requests.
    Affected if Webhooks are configured without requiring authentication or signature validation.
  4. Review webhook event processing logs
    Search Fleet controller logs for webhook-related entries, specifically looking for unauthenticated or unexpected webhook payloads that may indicate exploitation attempts.
    Affected if Logs show webhook requests from unknown sources or forged events targeting repositories.

A user is affected if their Fleet version is within the vulnerable ranges AND webhook endpoints are exposed without authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.12.15 / 0.13.11 / 0.14.6 or later
Fixed in 0.12.150.13.110.14.6
Interim mitigation

Upgrade to patched versions (0.15.2, 0.14.6, 0.13.11, 0.12.5 or later). Until patched, review and restrict webhook configurations to require authentication or limit exposure.

Recommended fix High confidence

Upgrade to Rancher Fleet 0.12.15 (for 0.12.x branch), 0.13.11 (for 0.13.x branch), 0.14.6 (for 0.14.x branch), or 0.15.2 (for 0.15.x branch)

  1. Identify your current Rancher Fleet version by checking the Fleet UI or running 'fleetctl version'
  2. Determine which version branch you're on (0.12.x, 0.13.x, 0.14.x, or 0.15.x)
  3. For Rancher-managed Fleet: Use the Rancher UI to upgrade Fleet to the latest patch version in your branch (0.12.15, 0.13.11, 0.14.6, or 0.15.2)
  4. For standalone/helm-managed Fleet: Run 'helm repo update' and then 'helm upgrade' to the appropriate patched release
  5. After upgrade, verify the new version is running: 'fleetctl version' should show the patched version
  6. Review Fleet webhook configurations to ensure only authenticated webhooks are enabled where possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rancher Fleet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44937 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44937 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data