CVE-2026-44256Public exploitNetwork attack vector

Unauthenticated log forgery via Basic-auth username newlines

Published Aug 19, 2026 · Updated Aug 19, 2026

Log injection in Wazuh Manager 4.4.0 through 4.14.5 and 5.0.0-beta1 allows remote attackers to forge API audit entries. The access-log middleware decodes the Basic-auth username before credential validation, and alogging.py inserts it into a plain-text line without escaping carriage returns or line feeds. An unauthenticated request to the reachable manager API is sufficient; the result is limited to forged or obscured audit records and downstream log poisoning, while JSON logs remain unaffected.

CVSS severity5.3
Medium
EPSS probability0.29%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Log injection in Wazuh Manager 4.4.0 through 4.14.5 and 5.0.0-beta1 allows remote attackers to forge API audit entries. The access-log middleware decodes the Basic-auth username before credential validation, and alogging.py inserts it into a plain-text line without escaping carriage returns or line feeds. An unauthenticated request to the reachable manager API is sufficient; the result is limited to forged or obscured audit records and downstream log poisoning, while JSON logs remain unaffected.

The record

CVE
CVE-2026-44256
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-117, CAPEC-268, CAPEC-81, CAPEC-93, T1562
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=>= 4.4.0, < 4.14.6
  2. Affected versionversion=>= 5.0.0-beta1, < 5.0.0-beta2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Wazuh · Wazuhversion=>= 4.4.0, < 4.14.6; version=>= 5.0.0-beta1, < 5.0.0-beta2

Published CVSS scores

5.3GitHub CNACVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-117Improper Output Neutralization for Logs
CAPEC-268Audit Log Manipulation
CAPEC-81Web Server Logs Tampering
CAPEC-93Log Injection-Tampering-Forging
T1562Impair Defenses

Public exploit references

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