Quick answers
- Is CVE-2026-44948 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44948 being exploited in the wild.
- How severe is CVE-2026-44948?
- Informational severity, with a CVSS score of 5.3, published 30 June 2026.
- Which products and versions are affected?
- Suse Fleet >=0.12.0, <0.12.16; >=0.13.0, <0.13.12; >=0.14.0, <0.14.7; >=0.15.0, <0.15.3.
- Is there a fix for CVE-2026-44948?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44948 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44948?
- Check whether you run 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.
Technical details
A path traversal vulnerability (CWE-22/CWE-23) exists in the Fleet ImageScan subsystem's GitRepo path handler. The Fleet controller fails to validate that resolved filesystem paths in 'gitrepo.Spec.Paths' remain within the cloned repository's temporary workspace. An authenticated attacker with RBAC permissions to create or modify GitRepo resources can use traversal sequences (e.g., '../../etc') to force the 'ScreeningLocalReader' to recursively walk directories outside the intended scope. This process consumes significant system resources and holds a global mutex, effectively blocking all ImageScan operations across the entire environment. The vulnerability is patched in versions 0.12.16, 0.13.12, 0.14.7, and 0.15.3.
Affected products
- SUSE Rancher Fleet >=0.12.0, <0.12.16; >=0.13.0, <0.13.12; >=0.14.0, <0.14.7; >=0.15.0, <0.15.3
Timeline
- 2026-06-29: advisory: GitHub Security Advisory published by Rancher
- 2026-06-30: disclosed: NVD publication date