dbcve.org
CWE-23Weakness · CWE-23

CVE-2026-44948

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 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
A path traversal vulnerability was found in Fleet's ImageScan subsystem in Rancher Fleet 0.12.0 up to 0.12.16, 0.13.0 up to 0.13.12, 0.14.0 up to 0.14.7 and 0.15.0 up to 0.15.3 could be used to traverse outside of the intended directory, causing a denial of service.

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

A path traversal vulnerability in Rancher Fleet's ImageScan subsystem (versions 0.12.0-0.12.16, 0.13.0-0.13.12, 0.14.0-0.14.7, and 0.15.0-0.15.3) allows attackers to traverse outside the intended directory, resulting in denial of service.

MitigationUpgrade to a patched version. If unavailable, implement input validation to restrict file paths in ImageScan to the intended directory boundaries and reject traversal sequences (../).

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

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Rancher Fleet version
    Check the installed Fleet version via the Rancher UI under 'Fleet' > 'Continuous Delivery' settings, or run 'helm list -n cattle-fleet-system' to list Fleet charts and their versions.
    Affected if The version falls within 0.12.0-0.12.16, 0.13.0-0.13.12, 0.14.0-0.14.7, or 0.15.0-0.15.3.
  2. Confirm ImageScan subsystem is active
    Check if ImageScan resources or controllers are present in the cluster: run 'kubectl get imagescans -A' or inspect Fleet controllers for ImageScan reconciler pods in the cattle-fleet-system namespace.
    Affected if ImageScan resources exist or the ImageScan controller is running in the Fleet namespace.
  3. Review ImageScan configurations for traversal exposure
    Examine any ImageScan custom resources (CRs) in the cluster: 'kubectl get imagescans -A -o yaml' and review the 'image' or 'scanJob' specifications for file path references.
    Affected if ImageScan CRs reference image tags or paths that could accept user-supplied input containing traversal sequences (../).
  4. Audit network exposure of Fleet controllers
    Check if the Fleet controller pods (fleet-agent, fleet-controller) are exposed externally via services or ingress: run 'kubectl get svc -n cattle-fleet-system' and review RBAC policies allowing unauthenticated or untrusted access.
    Affected if Fleet controllers with ImageScan are reachable from untrusted networks without additional authentication layers.

You are affected if Rancher Fleet is running a version between 0.12.0-0.12.16, 0.13.0-0.13.12, 0.14.0-0.14.7, or 0.15.0-0.15.3 AND the ImageScan subsystem is actively configured or processing image scan requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version. If unavailable, implement input validation to restrict file paths in ImageScan to the intended directory boundaries and reject traversal sequences (../).

Recommended fix Moderate confidence

Upgrade to the latest patch version in your current release branch (0.12.17+, 0.13.13+, 0.14.8+, or 0.15.4+); for long-term support, consider moving to the latest stable branch (e.g., 0.16.x or newer)

  1. Identify your current Rancher Fleet version using 'fleetctl version' or checking the Helm chart version
  2. For Fleet 0.12.x: Upgrade to version 0.12.17 or later
  3. For Fleet 0.13.x: Upgrade to version 0.13.13 or later
  4. For Fleet 0.14.x: Upgrade to version 0.14.8 or later
  5. For Fleet 0.15.x: Upgrade to version 0.15.4 or later
  6. If running a newer supported branch (e.g., 0.16.x), ensure you are on the latest patch release
  7. Verify the upgrade by checking 'fleetctl version' or the Fleet controller logs
Caveat Minor version upgrades within the same major.minor branch typically have no breaking changes; always review release notes before upgrading across major branches

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44948 — 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-44948 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