CVE-2026-50545 — Fission Environment CRD PodSpec Injection Enables Node Escape and Cluster Takeover

Vulnerability Overview

CVE-2026-50545 is a critical privilege escalation vulnerability (CVSS 9.9) in the Fission serverless framework, classified under CWE-269 (Improper Privilege Management), CWE-284 (Improper Access Control), and CWE-693 (Protection Mechanism Failure). The root cause lies in Fission's handling of Environment Custom Resource Definitions (CRDs): the framework fails to sanitize or restrict PodSpec fields supplied by users with CRD create/modify permissions. An attacker who can write to a Fission Environment CRD can inject arbitrary PodSpec configurations — mounting host filesystem paths, stripping securityContext constraints, or forcing privileged container execution — ultimately breaking out of the container boundary to the underlying Kubernetes node. A successful exploit can yield full cluster takeover.

Affected Software

• Product: github.com/fission/fission (Fission serverless framework for Kubernetes)
• Vendor ecosystem: Go
• Affected versions: all releases up to and including 1.23.0
• Patch available: No patch has been released as of the date of this write-up (disclosed 2026-06-30).

Exploitation Status

A public proof-of-concept (PoC) is available. This is not a theoretical issue — working exploit code is circulating, which materially lowers the bar for adversaries. The vulnerability was disclosed on 30 June 2026 and has not yet received a vendor patch, meaning every cluster running Fission ≤ 1.23.0 remains exposed. Defenders should treat this as actively exploitable and prioritise detection and compensating controls immediately. The attack surface is any principal (human user, service account, or CI/CD pipeline identity) that holds create or update RBAC permissions on Fission Environment CRDs.

How Our Detection Catches It

Our detection package ships coverage across seven SIEM platforms, targeting the observable artefacts produced at each stage of this attack chain.

Detection Logic

At a high level, the detection rules look for:

• Kubernetes audit log events recording CREATE or UPDATE operations on environments.fission.io resources where the request body contains privileged PodSpec fields — specifically hostPath volume mounts, privileged: true in securityContext, hostPID/hostNetwork/hostIPC flags, or capability additions such as SYS_ADMIN.
• Pod creation events spawned by the Fission controller shortly after a suspicious Environment CRD mutation, where the resulting pod exhibits node-escape indicators (host path mounts resolving to /etc, /var/run/docker.sock, /proc, or the container runtime socket).
• Process execution telemetry from the node showing unexpected processes launched from within a Fission builder or runner container namespace.

SIEM Coverage

• Microsoft Sentinel (KQL) — queries against AuditLogs and KubeAudit tables
• Splunk (SPL) — searches over Kubernetes audit sourcetypes
• Elastic (EQL) — event sequence rules correlating CRD mutation to privileged pod spawn
• IBM QRadar (AQL) — payload inspection on Kubernetes API server log events
• Sumo Logic — CIP queries on ingested audit streams
• Google Chronicle (YARA-L) — UDM-mapped detection for GKE and self-hosted clusters
• CrowdStrike (CQL) — Falcon sensor process and container telemetry correlation

Recommended Compensating Controls

Until a patch is available, restrict RBAC permissions on environments.fission.io to the minimum required set, enforce OPA/Gatekeeper or Kyverno policies that reject PodSpecs containing hostPath volumes or privileged: true, and audit existing Environment CRDs for injected fields.

For full detection queries, triage guidance, and atomic test cases mapped to MITRE ATT&CK, see the CVE-2026-50545 detection page.