Fleet Agent Fails to Filter Security Labels in Deployments

A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleDeployment.spec.options.namespaceLabels) when applying them to the target namespace. An attacker with git push access to a Fleet-monitored repository could overwrite Pod Security Standards (PSS) enforcement labels on a target namespace. This allows the attacker to weaken admission controls and deploy workloads that PSS policies would otherwise block.

Casky was already ahead

This CVE exploits attack patterns that Casky's 233matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-44938 exposes a critical vulnerability in Fleet's agent-side deployer that fails to sanitize security-sensitive namespace labels when applying configurations from fleet.yaml or BundleDeployment specifications. An attacker with repository access can inject malicious namespaceLabels that overwrite Pod Security Standards (PSS) enforcement labels on target Kubernetes namespaces. This allows them to systematically weaken admission controls and deploy non-compliant workloads that would normally be blocked by PSS policies. Organizations using Fleet for GitOps-based Kubernetes management face significant risk, as the attack requires only git push privileges—a common permission level for developers—yet grants the ability to bypass critical runtime security boundaries across their container infrastructure.

Casky's 233 matched skills leverage Claude AI with extended reasoning to detect this attack pattern by mapping to MITRE ATT&CK technique TA0006 (Credential Access) and analyzing the CWE-522 weakness (Insufficiently Protected Credentials). Practitioners using Casky would identify this threat through detection of: (1) unauthorized modifications to namespace labels via git commits, (2) PSS label overwrite attempts in BundleDeployment objects, (3) privilege escalation indicators following successful label tampering, and (4) deployment of workloads with security policies that deviate from organizational baselines. The platform's skill set would flag git-based lateral movement patterns, namespace-level privilege escalation, and policy bypass attempts—enabling security teams to correlate suspicious repository activity with subsequent container admission anomalies before malicious workloads execute.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

233 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-44938.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

cryptography · low

Run

MITRE ATT&CK Techniques

TA0006

Investigate the attack patterns behind CVE-2026-44938

Casky has 233 skills that investigate the attack patterns behind CVE-2026-44938. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn