Loading vulnerability…
Fission versions prior to 1.24.0 contain a security context validation bypass in Environment runtime and builder container fields. A tenant with RBAC permissions to create or update environments.fission.io objects can specify privileged containers, enable allowPrivilegeEscalation, or request dangerous Linux capabilities in the Fission function or builder namespace. These containers are then scheduled under the executor's high-privilege service account. This breaks the intended isolation boundary for tenant-supplied workloads and can permit escalation from a low-privileged tenant role to execution with excessive Kubernetes and node-level privileges.
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.
3 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.