CVE-2026-44256
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.4.0 until 4.14.6 and 5.0.0-beta2, api/api/middlewares.py decodes the Basic authentication username before credential validation and passes it to the access logger without neutralizing control characters. api/api/alogging.py interpolates that value into the plain-text API log. An unauthenticated attacker can include carriage returns or line feeds in the username to forge entries, obscure activity, or poison systems that consume the plain-text audit log. The JSON log format is not affected because JSON serialization escapes these characters. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- EPSS probability
- 0.29%
- CWE
- CWE-117
- Published
- 2026-08-19
- Last modified
- 2026-08-19
Affected products
- wazuh wazuh
- wazuh wazuh
Weakness type
Related vulnerabilities
- CVE-2026-14350 — Vulnerabilities exists in IBM Cloud Pak for Data System
- CVE-2026-9736 — Vulnerabilities exists in IBM Netezza Software
- CVE-2026-15603 — morgan vulnerable to Log Forging via unescaped Unicode line separators
- CVE-2026-81696 — openssl_encrypt before 1.4.9 Terminal Injection via info Command
- CVE-2026-81695 — openssl_encrypt before 1.4.9 Terminal Injection via key_id
- CVE-2026-81694 — verify-usb before 1.4.9 Output Injection via Unsanitized Filenames
- CVE-2026-54511 — @logtape/syslog: syslog log injection via unescaped control characters and unvalidated SD-NAME keys
- CVE-2026-74885 — openssl_encrypt before 1.4.0 Logging Bug and Race Condition