Local SQL injection via path interpolation
Published Aug 19, 2026 · Updated Aug 19, 2026
SQL injection in Wazuh 4.6.0 through 4.14.5 and 5.0.0-beta1 through 5.0.0-beta2 lets local users alter FIM query results via crafted filenames. DB::getFile() and DB::searchFile() in src/syscheckd/src/db/src/file.cpp build SQLite row filters by concatenating a monitored path, and the non-Windows FIMDBCreator::encodeString() path encoder does not neutralize SQL metacharacters before SQLite executes the resulting SELECT. Exploitation requires the ability to create a filename inside a File Integrity Monitoring directory on a non-Windows host; published testing showed UNION SELECT result-set manipulation and downstream FIM event tampering, not stacked statements or remote code execution.
Summary
What happened
SQL injection in Wazuh 4.6.0 through 4.14.5 and 5.0.0-beta1 through 5.0.0-beta2 lets local users alter FIM query results via crafted filenames. DB::getFile() and DB::searchFile() in src/syscheckd/src/db/src/file.cpp build SQLite row filters by concatenating a monitored path, and the non-Windows FIMDBCreator::encodeString() path encoder does not neutralize SQL metacharacters before SQLite executes the resulting SELECT. Exploitation requires the ability to create a filename inside a File Integrity Monitoring directory on a non-Windows host; published testing showed UNION SELECT result-set manipulation and downstream FIM event tampering, not stacked statements or remote code execution.
The record
- CVE
- CVE-2026-49392
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Wazuh
- Product
- Wazuh
- Classifications
- CWE-89, CWE-20
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.6.0, < 4.14.6
- Affected versionversion=>= 5.0.0-beta1, < 5.0.0-beta3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-9c4x-mrjh-rmw5 advisory proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo