CVE-2026-112341 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Wazuh versions from 4.0.0 before 4.14.9 have a SQL injection flaw in the WazuhDBBackend parameter handling. An authenticated user with agent:read on a single agent can use it to extract every agent's internal key.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running a Wazuh manager between 4.0.0 and 4.14.9 where some users hold the agent:read permission through the API. The attacker needs valid credentials, so exposure is limited to authenticated API users, but any such user can read every agent's internal key. Installations on 4.14.9 or later, or with no authenticated users beyond administrators, are less exposed.
Not affected if no-agent-read-users, version-4.14.9-or-later
Who cares self-hosted, siem, wazuh
/var/ossec/bin/wazuh-control info, if the sources' guidance applies to your install), and compare it against 4.14.9.4.14.9 or later, per the release notes linked from the sources.Wazuh versions from 4.0.0 before 4.14.9 contain a sql injection vulnerability in WazuhDBBackend._substitute_params due to sequential regex placeholder cross-contamination. Authenticated users with agent:read on one agent can inject UNION SELECT via the q and search parameters to extract every agent's internal_key through a blind boolean oracle on total_affected_items.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.