Loading story…
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.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
JFrog Security Research disclosed four vulnerabilities in Chaos Mesh, including three critical CVEs, and said deployments prior to version 2.7.3 were affected. JFrog reported the flaws could be chained from an unprivileged pod with in-cluster network access to achieve arbitrary command execution and possible full cluster takeover, and recommended upgrading to 2.7.3 or disabling the controller server.
ZeroPath published summaries covering CVE-2025-59358, CVE-2025-59359, CVE-2025-59360, and CVE-2025-59361 in Chaos Mesh. The reports described an authentication bypass and multiple command injection issues that could be chained for cluster-wide impact.
Chaos Mesh reportedly addressed the command injection vulnerabilities affecting the cleanTcs and cleanIptables mutations through GitHub pull request #4702. These flaws could allow arbitrary shell command execution in the Chaos Controller Manager.
Chaos Mesh publicly fixed the GraphQL authentication bypass vulnerability CVE-2025-59358 and coordinated disclosure with JFrog researchers. The flaw allowed unauthenticated access to the Controller Manager's exposed GraphQL debugging server where reachable from the cluster network.
A critical authentication bypass in the unsupported cockroach-k8s-request-cert container image was publicly described as affecting all versions due to an empty root password field in /etc/shadow. The summary noted Cockroach Labs had indicated remediation was left to users.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
6 references tracked. Mallory keeps watching after this page renders.
jfrog.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
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
Palo Alto Networks Unit 42 disclosed a dual privilege-escalation chain in **Google Kubernetes Engine (GKE)** that could let an attacker with limited access gain broader control inside Kubernetes environments. The attack path combined weaknesses in monitoring-related configuration and service mesh privileges, allowing unauthorized access to cluster resources and creating a route from a constrained foothold to elevated permissions. The reported chain involved **Fluent Bit** and **Anthos Service Mesh** components, showing how overly permissive configurations and inherited privileges in managed Kubernetes deployments can be linked together for escalation. The findings highlight the risk of misconfigured observability and mesh tooling in cloud-native environments, where service accounts, cluster roles, and add-on integrations can expand an attacker’s reach beyond the initial compromise if not tightly scoped.
Jul 3, 2026
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.
Jun 29, 2026