Loading vulnerability…
CVE-2026-50563 affects Fission, a Kubernetes-native serverless framework, in versions prior to 1.24.0. In the Container Executor path, a tenant can supply Function.spec.podspec directly. Fission merges this tenant-controlled pod specification into an executor-generated podspec and then creates a Kubernetes Deployment whose pods run the user-supplied container image. Because unsafe pod-level and container-level security settings can be injected through this merge process, an attacker can influence the resulting Deployment to run with elevated privileges or unsafe host integrations. Reported dangerous settings include hostPID, hostNetwork, hostIPC, hostPath volumes, serviceAccountName overrides, privileged containers, allowPrivilegeEscalation, and dangerous Linux capabilities. The issue is effectively a pod specification injection / improper authorization flaw in how Fission handles untrusted podspec input in the container executor workflow.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.