Loading story…
Two high-severity vulnerabilities in the Kubernetes-native serverless platform Fission were disclosed, both allowing low-privileged tenants to inject unsafe PodSpec fields that can lead to node escape and broader cluster compromise. CVE-2026-50563 affects the Container Executor path, where Function.spec.podspec could be merged into an executor-generated pod definition before a Deployment is created, while CVE-2026-50545 affects the Environment CRD path through insufficient validation of Environment.spec.runtime.podSpec and spec.builder.podSpec. Both issues carry a CVSS v3.1 rating of AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, reflecting low attack complexity and high impact to confidentiality, integrity, and availability.
The flaws affect Fission versions prior to 1.24.0, and the project has released fixes in version 1.24.0 alongside related GitHub advisories and pull requests. The disclosures indicate that unsafe passthrough and merge behavior in pod creation logic could let a tenant influence generated pods in ways that break isolation boundaries, turning serverless function deployment features into a path for host-level access and potential cluster takeover. Separately, a malicious Rust crate, onering 1.4.1, was also reported on the same day after being uploaded to crates.io with code designed to exfiltrate project metadata and source code before being removed roughly six hours later, though no evidence of actual use was reported.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-50566 was published as a high-severity vulnerability affecting Fission versions prior to 1.24.0. The flaw lets a tenant with environments.fission.io create or update permissions bypass SecurityContext restrictions to launch privileged containers under the executor's high-privilege service account, creating risk of sandbox escape and cluster compromise.
CVE-2026-50545 and CVE-2026-50563 were publicly disclosed as high-severity flaws affecting Fission before version 1.24.0. One involved Environment CRD podSpec handling and the other the Container Executor path, both enabling dangerous podSpec injection.
Fission released version 1.24.0 to patch both CVE-2026-50545 and CVE-2026-50563, which affected versions prior to 1.24.0. The flaws allowed unsafe podSpec fields to be merged into generated workloads, creating node escape risk.
The malicious onering 1.4.1 release remained available for about six hours before being removed from crates.io. The advisory said there was no evidence of actual usage and that the crate had no dependencies on crates.io.
A malicious version of the Rust package onering, version 1.4.1, was published to crates.io on June 10, 2026. The code attempted to exfiltrate project metadata and source code from projects that included the crate.
The vulnerability later tracked as CVE-2026-50545 was received by security-advisories@github.com on June 10, 2026. The issue affects Fission versions prior to 1.24.0 and can enable node escape and cluster takeover via podSpec passthrough handling.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcerustsec.org
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Kubernetes maintainers disclosed five critical vulnerabilities in **ingress-nginx**, including **`CVE-2025-1974`** with a **CVSS 9.8** rating, warning that attackers on the Pod network could abuse configuration injection in the Validating Admission Controller to take over clusters without credentials. The flaws also affect how ingress-nginx builds **NGINX** configuration from crafted Ingress objects, potentially exposing Secrets available to the controller and leading to full cluster compromise. Patched releases **`ingress-nginx v1.12.1`** and **`v1.11.5`** were issued, and operators were urged to upgrade immediately or temporarily disable the Validating Admission Controller until patching is complete. The disclosure adds to broader concerns about Kubernetes networking and multi-tenant isolation, highlighted by **`CVE-2021-25740`**, an unpatchable issue that lets users with permission to modify **Endpoint** or **EndpointSlice** objects redirect service traffic to unauthorized IP addresses. In shared ingress-controller or load-balancer deployments, that behavior can allow one tenant to steer traffic into another tenant’s workloads and bypass intended network boundaries. Security researchers and vendors said the combined risk is highest in clusters that rely on shared ingress infrastructure with broad Secret access, and recommended tightening EndpointSlice permissions, avoiding shared ingress designs in sensitive environments, and evaluating the **Gateway API** as a safer architecture.
Jun 29, 2026
JFrog Security Research disclosed four vulnerabilities in the Chaos Mesh chaos-engineering platform that can let attackers with in-cluster network access compromise Kubernetes environments, including three critical command-injection bugs and one authentication bypass. The issues, tracked as **CVE-2025-59358**, **CVE-2025-59359**, **CVE-2025-59360**, and **CVE-2025-59361**, affect Chaos Mesh deployments prior to **2.7.3** and stem from an exposed unauthenticated GraphQL server plus unsafe shell command construction in the `cleanTcs`, `killProcesses`, and `cleanIptables` mutations. JFrog said the default configuration can expose the GraphQL interface to any pod on the cluster, allowing even an unprivileged workload to reach vulnerable operations. Researchers reported that the flaws can be chained to invoke fault injections, execute arbitrary commands on pods and nodes, steal Kubernetes service account tokens, move laterally, and potentially take over an entire cluster. The command-injection bugs were rated **CVSS 9.8** and are especially dangerous because Chaos Mesh components such as the Controller Manager and Chaos Daemon typically run with elevated privileges. Chaos Mesh has issued fixes, including changes referenced in GitHub pull request **#4702**, and JFrog urged users to upgrade immediately to **Chaos Mesh 2.7.3** or disable the controller server through Helm as a temporary mitigation; platforms that integrate Chaos Mesh, including **Azure Chaos Studio for AKS**, may also be exposed.
Jun 29, 2026
Fission disclosed a high-severity flaw, tracked as **`CVE-2026-46614`** and **`GHSA-3g33-6vg6-27m8`**, that exposed internal per-function routes on the same public router listener used for normal `HTTPTrigger` traffic. In affected versions up to **1.22.0**, any party with network access to the router could call `/fission-function/<name>` or `/fission-function/<ns>/<name>` directly, even if no `HTTPTrigger` existed for that function. The behavior bypassed host, path, and method restrictions enforced by `HTTPTrigger`, potentially exposing unpublished functions, enabling function-name enumeration, and creating cross-tenant access risks in multi-tenant or internet-facing deployments. Fission fixed the issue in **version 1.23.0** by separating public and internal router listeners, moving direct function invocation to an internal **ClusterIP-only** service on port `8889`, and adding **HMAC-based authentication** for internal requests. The remediation also updated internal components including kubewatcher, timer, Kafka consumers, KEDA scaler components, fetcher, builder, and executor to use signed requests, while tightening `NetworkPolicy` controls and adding tests to block public access to `/fission-function/`. Until upgraded, operators were advised to restrict router ingress, block `/fission-function/` paths at the ingress layer, and avoid exposing the router directly through `LoadBalancer` or `NodePort`.
Jun 29, 2026