Loading story…
Wazuh disclosed a critical remote code execution flaw, CVE-2026-25769, affecting versions 4.0.0 through 4.14.2 when deployed in cluster mode. The vulnerability stems from unsafe JSON deserialization in cluster communications, where a custom object_hook can be abused to trigger attacker-controlled module imports and function execution on the master node. According to the advisory, an attacker who has already compromised a trusted worker can send a crafted payload through DAPI and execute arbitrary commands on the master, potentially with root privileges.
Because the master centrally manages workers, rules, and security processing, successful exploitation can lead to full cluster compromise, lateral movement, data theft, and evasion of security monitoring. Wazuh addressed the issue in 4.14.3 by introducing a deserialization allowlist, and defenders were urged to limit access to TCP port 1516, monitor worker integrity, segment cluster networks, and rotate cluster keys to reduce the risk of a compromised worker being used as a launch point against the master.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Public reporting documented that Wazuh 4.14.3 or later mitigates CVE-2026-25769 by introducing an allowlist for deserialization. The reporting also described how a compromised trusted worker could exploit the flaw to execute code on the master node and potentially compromise the cluster.
Wazuh published a security advisory for CVE-2026-25769, a remote code execution vulnerability caused by insecure deserialization in Wazuh cluster communications. The issue affects Wazuh versions 4.0.0 through 4.14.2 in cluster mode.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
resecurity.com
Open sourcegithub.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.
A critical `CVSS 10.0` vulnerability in **Wazuh Manager 5.0** allows a malicious or compromised agent to inject unauthorized OpenSearch bulk operations through the `inventory_sync` pipeline, enabling deletion of alerts, tampering with forensic evidence, and manipulation of backend SIEM data. The flaw stems from Wazuh forwarding the agent-controlled `DataValue.index` flatbuffer field into bulk `NDJSON` requests without proper escaping, causing injected `delete`, `index`, or `update` actions to run with the manager’s high-privilege OpenSearch credentials. Public reporting said the issue affects `wazuh-manager` from `5.0.0-beta1`, while `4.x` branches are not affected because they do not include the vulnerable inventory synchronization path. Researchers and public advisories said the exposure can be especially severe in deployments where `wazuh-authd` allows anonymous agent enrollment, potentially lowering the barrier to exploitation from authenticated abuse to practical unauthenticated access in some environments. Reported impacts include cross-index document deletion, post-compromise cleanup, persistent payload injection into saved dashboard objects, and interference with incident response and investigations. Wazuh fixed the issue in `5.0.0-beta3`, and the vulnerability is tracked as `GHSA-ff9g-85jq-r3g3`; defenders were urged to upgrade, disable anonymous enrollment, reduce indexer privileges, and review logs for unauthorized index modifications.
Jun 29, 2026
Wazuh disclosed **`CVE-2026-67308`**, a critical shell injection flaw in its GitHub Actions workflows that allows arbitrary command execution when attackers submit pull requests from public forks with a crafted `VERSION.json` file. The vulnerability affects workflows prior to commit `44bf114` and stems from attacker-controlled input being written to `GITHUB_ENV` and later interpolated directly into shell `run` steps, enabling shell metacharacters to execute through `bash`. The issue is classified as **CWE-78** and has been rated **CVSS 10.0** in public reporting, with the highest risk on **self-hosted runners** where exposed secrets may include **`GITHUB_TOKEN`** and **AWS credentials**. Wazuh remediated the flaw in commit `44bf114` and added hardening to additional workflows; public reporting said no active exploitation had been observed at publication, but noted the attack is low complexity and reachable through the project's public CI/CD pull request workflow.
Aug 2, 2026
Red Hat disclosed **CVE-2026-73268**, an Important-severity flaw in the `cluster-curator-controller` component of **Multicluster Engine for Kubernetes** that can let a tenant escalate privileges to the controller’s level. The issue stems from the `CreateJob()` function improperly unmarshaling user-controlled data from `spec.install.overrideJob` into a Kubernetes `Job` without validating dangerous fields, enabling arbitrary Job specification injection by users who can create or update `ClusterCurator` resources. Successful exploitation can cause the injected Job to run under the controller’s privileged ServiceAccount, potentially allowing arbitrary code execution, access to cluster-wide secrets, and control over managed cluster resources. Red Hat scored the bug **9.9 CVSS v3.1** and linked it to **CWE-94**; affected software includes `multicluster-engine/cluster-curator-controller-rhel9`. Recommended mitigations include applying vendor fixes, tightening **RBAC** so only trusted administrators can manage `clustercurators.cluster.open-cluster-management.io`, and reviewing controller privileges and validation controls around Job creation.
Aug 13, 2026