CVE-2026-44937: SUSE Rancher Fleet had an Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/rancher/fleetto a version that resolves this vulnerability.Fixed in 0.12.15 - Upgrade
Upgrade
go/github.com/rancher/fleetto a version that resolves this vulnerability.Fixed in 0.13.11 - Upgrade
Upgrade
go/github.com/rancher/fleetto a version that resolves this vulnerability.Fixed in 0.14.6 - Upgrade
Upgrade
go/github.com/rancher/fleetto a version that resolves this vulnerability.Fixed in 0.15.2 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in v0.15.2 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in v0.14.6 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in 0.13.11 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in 0.12.15 - 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
Frequently Asked Questions
What is the severity of CVE-2026-44937?
The severity of CVE-2026-44937 is rated high with a score of 7.5.
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.
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.
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.
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.