CVE-2026-44256: Wazuh: CRLF Log Injection via Unsanitized Basic-Auth Username

Published Aug 19, 2026
·
Updated

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.

Affected Software

1 affected component
Wazuh Wazuh>=4.4.0<4.14.6, =5.0.0-beta2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Wazuh to a version that resolves this vulnerability.

    Fixed in 4.14.6
  2. Upgrade

    Upgrade Wazuh to a version that resolves this vulnerability.

    Fixed in 5.0.0-beta2

Event History

Aug 19, 2026
CVE Published
via MITRE·04:21 PM
Data Sourced
via MITRE·04:21 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Wazuh versions from 4.4.0 through 4.14.6, and version 5.0.0-beta2, are identified as affected when using the plain-text API log format. The JSON log format is not affected.

2

Does exploitation require valid API credentials or user interaction?

No. An unauthenticated network attacker can supply carriage return or line feed characters in a Basic Authentication username before credential validation.

3

What is the impact of a successful exploit?

An attacker can forge plain-text API log entries, obscure activity, or poison systems that consume the audit log. The stated impact is limited to log integrity; confidentiality and availability are not affected.

4

What should be done if upgrading is not immediately possible?

Use the JSON API log format, which escapes these characters and is not affected, rather than the plain-text API log format. Review plain-text API logs and any downstream systems consuming them for potentially forged or malformed entries.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203