CVE-2026-44937: SUSE Rancher Fleet had an Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components

Published Jul 1, 2026
·
Updated

Impact A vulnerability has been identified in Fleet when the webhook endpoint is configured without a secret; an attacker can forge webhook requests. The attacker doesn't need to know the specific repository or path configured in the GitRepo resource to make Fleet process these requests.

An attacker can exploit this vulnerability to cause the following impacts: 1. Trigger continuous repository re-cloning, which increases network traffic and can deplete resources on the management cluster. 2. Downgrade running services to any historical revision available in the remote Git repository. This risk applies if the attacker has read access to the target Git repository and knows its configured path.

Please consult the associated MITRE ATT&CK - Technique - T1499.004: Endpoint Denial of Service for further information about this category of attack.

Patches To resolve this vulnerability, upgrade Fleet to a patched version. This upgrade version escapes the URL and path to the remote repository received from webhooks, which prevents regular expressions from being used as a replacement for the URL and path.

Patched versions of Fleet include releases v0.15.2, v0.14.6, 0.13.11, and v0.12.15.

Workarounds If you can't upgrade to a fixed version, please make sure to only enable webhooks with a shared secret.

Credits

This security issue was reported by the following collaborators according to our responsible disclosure policy:

- Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC).

References If you have any questions or comments about this advisory: - Reach out to the SUSE Rancher Security team for security related inquiries. - Open an issue in the Rancher repository. - Verify with our support matrix and product support lifecycle.

Other sources

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.

MITRE

Affected Software

8 affected componentsFixes available
go/github.com/rancher/fleet>=0.12.0<0.12.15
0.12.15
go/github.com/rancher/fleet>=0.13.0<0.13.11
0.13.11
go/github.com/rancher/fleet>=0.14.0<0.14.6
0.14.6
go/github.com/rancher/fleet>=0.15.0<0.15.2
0.15.2
SUSE Rancher Fleet>=0.12.0<0.12.15
SUSE Rancher Fleet>=0.13.0<0.13.11
SUSE Rancher Fleet>=0.14.0<0.14.6
SUSE Rancher Fleet>=0.15.0<0.15.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/rancher/fleet to a version that resolves this vulnerability.

    Fixed in 0.12.15
  2. Upgrade

    Upgrade go/github.com/rancher/fleet to a version that resolves this vulnerability.

    Fixed in 0.13.11
  3. Upgrade

    Upgrade go/github.com/rancher/fleet to a version that resolves this vulnerability.

    Fixed in 0.14.6
  4. Upgrade

    Upgrade go/github.com/rancher/fleet to a version that resolves this vulnerability.

    Fixed in 0.15.2
  5. Upgrade

    Upgrade SUSE Rancher Fleet to a version that resolves this vulnerability.

    Fixed in v0.15.2
  6. Upgrade

    Upgrade SUSE Rancher Fleet to a version that resolves this vulnerability.

    Fixed in v0.14.6
  7. Upgrade

    Upgrade SUSE Rancher Fleet to a version that resolves this vulnerability.

    Fixed in 0.13.11
  8. Upgrade

    Upgrade SUSE Rancher Fleet to a version that resolves this vulnerability.

    Fixed in 0.12.15
  9. Configuration

    If you cannot upgrade to one of the patched Fleet versions, ensure only webhooks are enabled with a shared secret (avoid configuring the Fleet webhook endpoint without a secret).

    SUSE Rancher Fleet (webhook configuration) webhook secret = required

Event History

Jul 1, 2026
Advisory Published
via GitHub·08:44 PM
Data Sourced
via GitHub·08:44 PM
DescriptionSeverityWeaknessAffected Software
Jul 6, 2026
CVE Published
via MITRE·09:52 AM
Data Sourced
via MITRE·09:52 AM
DescriptionWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44937?

The severity of CVE-2026-44937 is rated high with a score of 7.5.

2

How do I fix CVE-2026-44937?

To fix CVE-2026-44937, configure the webhook endpoint in Fleet with a unique secret to prevent unauthorized requests.

3

What type of attacks can be carried out using CVE-2026-44937?

CVE-2026-44937 allows attackers to forge webhook requests without needing knowledge of the specific repository or path.

4

What impact does CVE-2026-44937 have on Fleet users?

CVE-2026-44937 can lead to unauthorized processing of webhook requests, compromising the integrity of Fleet operations.

5

Is authentication required to exploit CVE-2026-44937?

No, CVE-2026-44937 does not require authentication to exploit as it allows unauthenticated attacks through forged requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203