CVE-2026-49822: Fission Kubernetes Namespace Isolation Bypass via KubernetesWatchTrigger

Technical summary

CVE-2026-49822 stems from improper access control in Fission's KubernetesWatchTrigger implementation. The vulnerability allows a low-privilege user (PR:L) to craft a KWT resource that, when created in one namespace, can establish a persistent watch channel over arbitrary other namespaces. This violates the principle of least privilege and Kubernetes' namespace isolation model. The attack requires network access (AV:N) but no user interaction (UI:N), and the impact crosses namespace boundaries (S:C), resulting in confidentiality compromise (C:H). The underlying root cause relates to insufficient authorization checks (CWE-862) and improper restriction of namespace-level operations (CWE-284).

Business impact

Multi-tenant Kubernetes clusters running Fission become vulnerable to cross-namespace espionage. A developer with limited scope—perhaps sandboxed to a single project namespace—can covertly monitor production workloads, secrets, ConfigMaps, and function execution logs in other namespaces. This exposes sensitive business logic, credentials, and operational data. The persistent nature of the surveillance channel makes detection difficult and extends exposure window. Organizations relying on namespace isolation for compliance or cost-center separation face control breakdown.

Affected systems

Fission versions prior to 1.24.0 are affected. Any Kubernetes cluster deploying Fission and relying on namespace-level access controls is at risk, particularly multi-tenant clusters where different teams or projects operate in separate namespaces. The vulnerability is exploitable by any user with KWT creation permissions in their namespace, regardless of their overall cluster privilege level.

Exploitability

Exploitability is high. The attack requires only low privileges (developer-level access to create resources in a namespace) and network connectivity to the Kubernetes API. No user interaction is needed, and the exploit path is straightforward: create a malicious KWT resource. However, this vulnerability is not yet in CISA's Known Exploited Vulnerabilities (KEV) catalog, suggesting active exploitation in the wild has not been documented at time of disclosure. The barrier to weaponization is low, making prompt patching critical before threat actors adapt.

Remediation

Upgrade Fission to version 1.24.0 or later. Organizations unable to upgrade immediately should implement restrictive RBAC policies limiting KWT creation to trusted service accounts, and apply network policies to restrict watch channel communication. Monitor audit logs for suspicious KWT creation in non-production namespaces. Consider running separate Fission control planes per tenant environment as a compensating control.

Patch guidance

Verify the availability of Fission 1.24.0 or later through your deployment mechanism (Helm, package manager, direct image pull). Review vendor advisories and release notes to confirm the patch fully addresses this vulnerability. Test the upgrade in a non-production Kubernetes cluster first, ensuring backward compatibility with existing KWT and function definitions. Plan a maintenance window and perform a rolling update of the Fission controller and related components to minimize service disruption.

Detection guidance

Monitor Kubernetes audit logs for KubernetesWatchTrigger resource creation events, especially in namespaces where function deployment is unexpected. Look for patterns where a single user or service account creates KWTs across multiple namespaces. Implement monitoring on apiserver watch channels to detect anomalous cross-namespace observation. Use tools like Falco or eBPF-based runtime security to detect process-level watch handle creation by Fission components. Flag cases where watch channels persist longer than typical function invocation durations.

Why prioritize this

This vulnerability merits urgent attention (CVSS 7.7 HIGH) due to the combination of low exploitation barriers, cross-namespace impact, and confidentiality compromise. While not yet in the KEV catalog, the ease of attack and the sensitive data at risk—particularly in multi-tenant production clusters—justify immediate patching. Organizations with strict compliance requirements around data isolation should treat this as critical.

Risk score, explained

The CVSS 7.7 score reflects the high confidentiality impact (C:H) in a scenario where namespace isolation is broken (S:C), combined with low barriers to exploitation (AC:L, PR:L, AV:N). The lack of integrity or availability impact moderates the score from critical. In high-risk environments (e.g., regulatory, SaaS platforms, or competitive industries), the contextual risk is substantially higher than the base score suggests.

Frequently asked questions