CVE-2026-56699
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWazuh Manager before 5.0.0-beta3 fails to escape the DataValue.index field when constructing OpenSearch bulk requests, allowing enrolled agents to inject arbitrary NDJSON operations. Attackers can smuggle delete, index, or update operations into bulk requests executed under the manager's admin credentials, enabling document deletion, alert tampering, and cross-agent SIEM state manipulation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWazuh Manager before 5.0.0-beta3 does not properly escape/sanitize the DataValue.index field when constructing OpenSearch bulk API requests. Since enrolled agents control this field value, attackers can inject arbitrary NDJSON operations (delete, index, update) that are executed with the manager's administrative OpenSearch credentials, enabling document deletion, alert tampering, and cross-agent SIEM state manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Wazuh Manager versionRun 'wazuh-control info' or check '/var/ossec/bin/wazuh-control info' to retrieve the installed Wazuh Manager version. Alternatively, inspect the file '/var/ossec/usr/ossec/bin/wazuh-modulesd' or check the Wazuh API endpoint /manager/infoAffected if The version is lower than 5.0.0-beta3 (e.g., 5.0.0-beta2, 4.x.x, or earlier)
-
Confirm OpenSearch integration is enabledCheck the Wazuh Manager configuration file at /var/ossec/etc/ossec.conf for any <indexer> or <opensearch> sections, or inspect the output of 'wazuh-logtest' for OpenSearch-related modules. Also check if the 'wazuh-indexer' or 'opensearch' service is runningAffected if OpenSearch or Wazuh Indexer is configured and actively used by the manager (the vulnerability affects the OpenSearch bulk request construction)
-
Verify agent registration is permittedReview /var/ossec/etc/ossec.conf for <auth> or <cluster> settings, and check if agent enrollment is enabled. Inspect /var/ossec/etc/agent.conf for agent configuration allowancesAffected if Agent registration or enrollment is enabled, allowing authenticated agents to communicate with the manager (authenticated agents are the attack vector)
-
Check for suspicious bulk API activityReview OpenSearch or Wazuh Indexer logs (typically in /var/log/wazuh-indexer/ or /var/log/opensearch/) for unusual bulk request patterns, particularly DELETE, INDEX, or UPDATE operations that originate from the Wazuh Manager's bulk API endpointAffected if Bulk requests contain unexpected index names or operations that were not explicitly initiated by legitimate manager functions
The environment is affected if Wazuh Manager version is below 5.0.0-beta3 AND OpenSearch/Wazuh Indexer integration is enabled, allowing authenticated agents to potentially inject operations into bulk requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Wazuh Manager to version 5.0.0-beta3 or later which properly escapes the DataValue.index field in bulk requests. Until patched, monitor OpenSearch bulk API logs for anomalous operations originating from agent-supplied index values.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56699 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data