Is CVE-2026-56699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56699 being exploited in the wild.

How severe is CVE-2026-56699?

Critical severity, with a CVSS score of 10, published 15 July 2026.

Which products and versions are affected?

Wazuh Wazuh Manager >= 5.0.0-beta1, < 5.0.0-beta3.

Is there a fix for CVE-2026-56699?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-56699 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-56699?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56699: Wazuh Manager NDJSON injection in inventory_sync

Q: Is there a fix for CVE-2026-56699?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-56699 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-56699?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56699 · Severity: critical · CVSS 10 · Published 2026-07-15

Wazuh Manager, a central component of the Wazuh security monitoring platform, contains a vulnerability that allows managed agents to bypass security controls. By sending specially crafted data, a compromised or malicious agent can trick the manager into executing unauthorized commands on the backend database. This can lead to the deletion of security alerts, tampering with inventory data for other systems, and the destruction of forensic evidence.

Quick answers

Is CVE-2026-56699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56699 being exploited in the wild.
How severe is CVE-2026-56699?: Critical severity, with a CVSS score of 10, published 15 July 2026.
Which products and versions are affected?: Wazuh Wazuh Manager >= 5.0.0-beta1, < 5.0.0-beta3.
Is there a fix for CVE-2026-56699?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-56699 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56699?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An NDJSON injection vulnerability exists in the inventory_sync subsystem of Wazuh Manager. The component fails to escape the 'DataValue.index' field when constructing OpenSearch _bulk requests, allowing an enrolled agent to smuggle arbitrary operations (delete, index, update) into the request stream. Because the manager typically connects to the wazuh-indexer using administrative credentials (all_access role), these smuggled operations execute with full privileges. Attackers can exploit this to delete documents in any wazuh-* index, manipulate SIEM state for other agents, or inject malicious payloads into Kibana saved objects. The vulnerability is present in the 5.0.0-beta1 and beta2 releases and is fixed in 5.0.0-beta3.

Affected products

Wazuh Wazuh Manager >= 5.0.0-beta1, < 5.0.0-beta3

Timeline

2026-06-08: advisory: GitHub Security Advisory published
2026-07-15: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.