CVE-2026-44938
Git-push can overwrite namespace PSS labels in Fleet, weakening admission controls.
Is CVE-2026-44938 being exploited?
Not confirmed. CVE-2026-44938 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-44938?
CVE-2026-44938 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44938?
Yes. A fix has been recorded for CVE-2026-44938. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44938 affect?
CVE-2026-44938 affects Fleet agent-side deployer, fleet.yaml, BundleDeployment.spec.options.namespaceLabels, Fleet-monitored Git repositories, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44938?
Restrict git push, sanitize namespaceLabels, rotate repo creds, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker with git push access can overwrite Pod Security Standard labels, bypass namespace admission controls, and deploy workloads PSS would block (may enable privileged containers).
Patch when possible
- affected>= 0.15.0 and < 0.15.2
- affected>= 0.14.0 and < 0.14.6
- affected>= 0.13.0 and < 0.13.11
- affected>= 0.12.0 and < 0.12.15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.