CVE-2026-50545: Fission Environment CRD PodSpec Injection Leading to Node Escape and Cluster Takeover
Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, the Environment.spec.runtime.podSpec / spec.builder.podSpec passthrough lacked validation, and MergePodSpec propagated dangerous fields into the generated pods. This issue has been patched in version 1.24.0.
Metrics
- CVSS v3.1
- 9.9
- Severity
- CRITICAL
- Fixed in
- —
- Affected Products
- 1
HarborGuard Analysis
Synopsis
This is a PodSpec injection vulnerability in the Fission Kubernetes-native serverless framework affecting versions prior to 1.24.0. An authenticated attacker with low-privilege access can reach the vulnerable API over the network and inject arbitrary fields into the PodSpec of generated pods, which propagate through the MergePodSpec mechanism without validation. Successful exploitation allows the attacker to escape the pod sandbox, gain control of the underlying node, and achieve full cluster takeover. HarborGuard tracks this advisory and will make a patched-image rebuild available the moment an upstream fix is published.
HarborGuard Coverage
Detection for CVE-2026-50545 is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against all customer images, including custom-built images that bundle Fission components. Any image found running an affected version of Fission is flagged immediately in the pipeline scan results.
AvailableHarborGuard is capable of scoring this CVE at CVSS 9.9 Critical and weighting the result against each environment's compliance policy to determine breach of policy thresholds. Triage findings are routable to the appropriate team inbox within each customer organization based on workload ownership rules.
AvailableBecause no upstream fix version has been published for this CVE, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment Fission 1.24.0 or a later remediated release is confirmed upstream. For customers with auto-remediation enabled, the rebuild, regression test run, and PR against affected workloads will be triggered without manual intervention as soon as the fix becomes available.
Pending upstreamExploit Conditions
- Network reachabilityRequired
The attacker must reach the Fission API service over the network; the vulnerability is exposed via a network-accessible endpoint.
- AuthenticationRequired
A valid account is required, but any low-privilege credential is sufficient; no administrative role is needed.
- Victim interactionNot required
No user interaction is needed; the attacker can trigger the injection entirely on their own.
- Attack complexityDetail
Exploitation is reliable and condition-free; no race condition, specific memory layout, or environmental prerequisite is required.
Blast Radius
- A successful attacker can inject privileged or host-path mounts into generated pod definitions, breaking out of the pod sandbox onto the underlying Kubernetes node.
- With node-level access, the attacker reads secrets, service-account tokens, and kubeconfig material stored on the node, exposing cluster credentials.
- The attacker can modify or delete workloads and persistent data across the cluster by using the harvested cluster credentials.
- Node compromise in a shared cluster disrupts all workloads co-scheduled on that node, causing service outages beyond the Fission environment itself.
How HarborGuard Handles This
Available on HarborGuard: because no upstream fix has been published for CVE-2026-50545, HarborGuard continuously re-evaluates the advisory on each ingest cycle and will surface a patched-image rebuild the moment Fission 1.24.0 is confirmed available. For customers who opt into auto-remediation, the full flow (rebuild, regression test run, and PR opened against affected workloads) will trigger automatically without requiring manual action. While no patch exists, customers can apply compensating controls through HarborGuard policy: network-policy isolation rules can restrict which principals may reach the Fission API server, admission-controller policies can be enforced to block PodSpec fields that carry hostPath volumes or privileged escalation flags, and environments that do not require the Fission builder component can gate it off via feature-flag configuration. HarborGuard will emit a re-triage notification to the configured team inbox as soon as upstream status changes.
- fission / fission< 1.24.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H