{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44256 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44256 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44256 is a medium-severity vulnerability in Wazuh Wazuh, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44256 and fix it if it is affected.\n\nWhat it is: CVE-2026-44256 is a medium-severity vulnerability in Wazuh Wazuh, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44256 in the wild and no public exploit code.\n\nAffected product: Wazuh Wazuh. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44256/ (Markdown: https://insights.sbomify.com/CVE-2026-44256/index.md)","id":"CVE-2026-44256","markdown":"https://insights.sbomify.com/CVE-2026-44256/index.md","name":"CVE-2026-44256","record":{"aliases":["GHSA-c3m6-fp2h-wmr4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wazuh security platform","requires_auth":"none","summary":"Unauthenticated attackers can inject CRLF characters into API logs via Basic Auth usernames, potentially forging log entries or obscuring activity.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wazuh","vendor":"wazuh"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Wazuh: CRLF Log Injection via Unsanitized Basic-Auth Username","id":"CVE-2026-44256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wazuh:wazuh","products":["wazuh:wazuh"],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"efw4.X: RCE via zipslip","id":"CVE-2026-44257"},"packages":[],"prev":{"headline":"Wazuh: Username Enumeration via Timing Side-Channel","id":"CVE-2026-44255"},"products":["wazuh"],"published":"2026-08-19","related":[{"cvss_score":9.9,"headline":"Wazuh Server Deserialization of Untrusted Data","id":"CVE-2025-24016","kev_date_added":"2025-06-10","published":"2025-02-10"},{"cvss_score":9.8,"headline":"Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2024-32038","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-44079","kev_date_added":null,"published":"2021-11-22"},{"cvss_score":9.5,"headline":"Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft","id":"CVE-2024-1243","kev_date_added":null,"published":"2025-06-11"},{"cvss_score":9.1,"headline":"Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)","id":"CVE-2026-61800","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.1,"headline":"Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager","id":"CVE-2026-48024","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":9.1,"headline":"Path traversal in wazuh","id":"CVE-2026-48162","kev_date_added":null,"published":"2026-08-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["wazuh"]},"summary":"Unauthenticated attackers can inject CRLF characters into API logs via Basic Auth usernames, potentially forging log entries or obscuring activity.","url":"https://insights.sbomify.com/CVE-2026-44256/"}