Loading story…
Red Hat OpenShift Service Mesh was the subject of multiple security advisories, including a broader notice covering multiple vulnerabilities and a follow-on advisory identifying a flaw in Kiali, the service mesh observability and management component, that could allow denial of service. The issues affect deployments using OpenShift Service Mesh and highlight risk in both the core platform and associated management tooling.
The advisories from dCERT indicate that organizations running Red Hat OpenShift Service Mesh should review vendor guidance and assess exposure in environments where Kiali is enabled, as service disruption could affect visibility and management of mesh traffic. Together, the notices point to a need for prompt patching and validation of Service Mesh components to reduce the chance of outages or abuse of vulnerable functionality.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
dCERT published Advisory 2026-0472 for Red Hat OpenShift Service Mesh, stating that a vulnerability in Kiali could allow denial of service. No additional exploit or remediation details are included in the reference.
dCERT published Advisory 2025-2592 covering multiple vulnerabilities affecting Red Hat OpenShift Service Mesh. The reference does not provide further technical details or a separate disclosure date beyond publication.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
Red Hat disclosed two high-severity vulnerabilities in OpenShift AI that could let authenticated attackers access other tenants’ resources and sensitive Kubernetes credentials. **CVE-2025-12805** affects the `llama-stack-operator`, where a missing `NetworkPolicy` left the Llama Stack service endpoint reachable across namespaces. Red Hat said a user in one namespace could directly access another user’s Llama Stack instance and potentially view or manipulate sensitive data, with the issue tracked under **CWE-653** and rated `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`. A second flaw, **CVE-2026-5483**, impacts the `odh-dashboard` component and can expose Kubernetes Service Account tokens through a Node.js endpoint. Red Hat warned that disclosure of those tokens could enable unauthorized access to Kubernetes resources; the issue is mapped to **CWE-201** and carries the vector `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`. Red Hat published CVE records, Bugzilla entries, and errata references for both vulnerabilities, highlighting risks to confidentiality and integrity in multi-tenant OpenShift AI deployments.
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
Red Hat OpenShift Pipelines was the subject of multiple security advisories, including one affecting the **Fulcio** component used by the OpenShift Pipelines Operator. One disclosed flaw was reported to allow **denial of service**, raising the risk of service disruption in environments that rely on the operator’s signing and pipeline-related functionality. A later advisory reported **multiple vulnerabilities** in Red Hat OpenShift Pipelines, indicating broader security exposure beyond the previously disclosed Fulcio issue. Organizations running OpenShift Pipelines should review the affected product versions, assess exposure across pipeline and operator deployments, and prioritize vendor-recommended updates or mitigations to reduce the risk of disruption or further compromise.
Jun 29, 2026