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

Upgrade to Pro
CVE-2026-50566

Fission SecurityContext Bypass Privileged Pod Creation (CVE-2026-50566)

Detects exploitation of CVE-2026-50566, a critical (CVSS 9.9) vulnerability in Fission (<= 1.23.0) where the Environment Runtime.Container and Builder.Container SecurityContext fields can be manipulated to bypass intended pod security restrictions, allowing creation of privileged pods within the Kubernetes cluster. Attackers with Fission Environment/Function CRUD access can escalate to node-level or cluster-level compromise by deploying privileged containers via the executor's pod spec generation, bypassing SecurityContext hardening (e.g. privileged: true, allowPrivilegeEscalation, hostPID, hostNetwork, capabilities such as SYS_ADMIN). This detection focuses on Kubernetes audit log events showing creation/update of Fission Environment CRDs with permissive securityContext blocks and subsequent pod creation events reflecting privileged escalation in namespaces managed by Fission (typically fission-function, fission-builder).

Vulnerability Intelligence

Public PoC

What is CVE-2026-50566 Fission SecurityContext Bypass Privileged Pod Creation (CVE-2026-50566)?

Fission SecurityContext Bypass Privileged Pod Creation (CVE-2026-50566) (CVE-2026-50566) maps to the Privilege Escalation and Initial Access and Defense Evasion tactics — the adversary is trying to gain higher-level permissions in MITRE ATT&CK.

This page provides production-ready detection logic for Fission SecurityContext Bypass Privileged Pod Creation (CVE-2026-50566), covering the data sources and telemetry it touches: Kubernetes Audit Logs, Azure Kubernetes Service Diagnostic Logs. The queries below are rated critical severity at high confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Privilege Escalation Initial Access Defense Evasion
Microsoft Sentinel / Defender
kusto
let PrivilegedFlags = dynamic(["privileged","allowPrivilegeEscalation","hostPID","hostNetwork","hostIPC","SYS_ADMIN"]);
KubeAuditLogs
| where Verb in ("create","update","patch")
| where ObjectRef_Resource in ("environments","pods")
| where ObjectRef_Namespace has_any ("fission-function", "fission-builder", "fission")
| where RequestObject has_any (PrivilegedFlags)
| extend PodName = tostring(ObjectRef_Name), Namespace = tostring(ObjectRef_Namespace), User = tostring(User_Username)
| where RequestObject has "true" and (RequestObject has "privileged" or RequestObject has "allowPrivilegeEscalation")
| project TimeGenerated, User, Verb, ObjectRef_Resource, Namespace, PodName, RequestObject
| order by TimeGenerated desc

Detects Kubernetes API audit events where Fission Environment or Pod objects in fission-managed namespaces are created/modified with permissive SecurityContext fields indicating exploitation of CVE-2026-50566.

critical severity high confidence

Data Sources

Kubernetes Audit Logs Azure Kubernetes Service Diagnostic Logs

Required Tables

KubeAuditLogs

False Positives

  • Legitimate cluster administrators intentionally deploying privileged workloads for infrastructure components (CNI, storage drivers)
  • Fission upgrade to patched version 1.24.0 which may still show securityContext fields during migration
  • CI/CD pipelines that deploy privileged debug/test environments in non-production clusters

Sigma rule & cross-platform mapping

The detection logic for Fission SecurityContext Bypass Privileged Pod Creation (CVE-2026-50566) (CVE-2026-50566) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  product: azure

Browse the community-maintained Sigma rules for this technique:


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 1Create Fission Environment with Privileged SecurityContext

    Expected signal: Kubernetes audit log entry showing a 'create' verb against the environments resource in fission-function namespace with requestObject containing privileged:true and allowPrivilegeEscalation:true.

  2. Test 2Deploy Function Triggering Privileged Pod via Builder Container

    Expected signal: Kubernetes audit log showing 'update' verb on environments resource with builder.container.securityContext containing privileged:true and hostPID:true, followed by pod creation events in fission-builder namespace.

  3. Test 3Verify Privileged Pod Escapes to Host Filesystem

    Expected signal: Container runtime and host-level audit logs showing a process from within the fission-function namespace pod performing a chroot/mount operation accessing the host root filesystem (/proc/1/root).

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-50566 — 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