Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-50564.

Upgrade to Pro
CVE-2026-50564 Elastic Security · Elastic

Detect Fission Environment CRD PodSpec Passthrough Node Escape (CVE-2026-50564) in Elastic Security

Fission (<=1.23.0) allows the Environment Custom Resource podspec passthrough (poolspec.container / poolspec.podspec) to inject arbitrary Kubernetes PodSpec fields including hostPID, hostNetwork, hostIPC, and privileged securityContext into builder/executor pods created by the fission-builder and fission-router controllers. Any principal able to create or update Environment CRDs (which in many multi-tenant Fission deployments includes low-privileged function developers) can escalate to full node compromise by scheduling a privileged, host-namespace-sharing pod, then pivoting to the underlying kubelet, container runtime socket, or other pods on the node. CVSS 9.9.

MITRE ATT&CK

Tactic
Privilege Escalation Lateral Movement Initial Access

Elastic Detection Query

Elastic Security (Elastic)
eql
any where event.dataset == "kubernetes.audit" and
  kubernetes.audit.objectRef.resource == "environments" and
  kubernetes.audit.verb in ("create", "update", "patch") and
  (stringContains(kubernetes.audit.requestObject, "hostPID") or
   stringContains(kubernetes.audit.requestObject, "hostNetwork") or
   stringContains(kubernetes.audit.requestObject, "hostIPC") or
   stringContains(kubernetes.audit.requestObject, "privileged\":true"))
critical severity high confidence

EQL rule over Elastic Kubernetes audit integration flagging Fission Environment resource writes with privileged/host-namespace podspec passthrough fields.

Data Sources

Kubernetes Audit Logs (Elastic Kubernetes Integration)

Required Tables

logs-kubernetes.audit_logs

False Positives & Tuning

  • Legitimate privileged environment templates approved for hardware-in-the-loop CI runners
  • Cluster add-on operators re-applying environment CRDs with host networking during upgrades
  • False match on unrelated CRD types sharing similarly-named fields if resource filter is loosened

Other platforms for CVE-2026-50564


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Deploy Fission Environment with hostPID and privileged podspec passthrough

    Expected signal: Kubernetes API audit log entry (verb=create) for environments.fission.io/atomic-test-hostpid-env containing hostPID:true and securityContext.privileged:true in the request object.

  2. Test 2Deploy Fission Environment with hostNetwork passthrough

    Expected signal: Kubernetes API audit log entry (verb=create) for environments.fission.io/atomic-test-hostnet-env containing hostNetwork:true in the request object.

  3. Test 3Patch existing Fission Environment to add hostIPC after initial benign creation

    Expected signal: Kubernetes API audit log entries for both create and patch verbs on environments.fission.io/atomic-test-patch-env, with the patch event's requestObject containing hostIPC:true and privileged:true.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-50564 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections