{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41499 exists.","fix":"No fix has been published for CVE-2026-41499 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41499 is a medium-severity memory corruption vulnerability in Wazuh Wazuh, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41499 and fix it if it is affected.\n\nWhat it is: CVE-2026-41499 is a medium-severity memory corruption vulnerability in Wazuh Wazuh, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41499 exists.\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-41499/ (Markdown: https://insights.sbomify.com/CVE-2026-41499/index.md)","id":"CVE-2026-41499","markdown":"https://insights.sbomify.com/CVE-2026-41499/index.md","name":"CVE-2026-41499","record":{"aliases":["GHSA-qvqj-p8mm-r7h3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Wazuh security platform","requires_auth":"low_privilege","summary":"Attackers can trigger heap corruption via crafted agent data, potentially leading to code execution or service crashes in Wazuh.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wazuh","vendor":"wazuh"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"},{"id":"CWE-124","name":"Buffer Underwrite"}],"description":"Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 4.0.0 to before version 4.14.4, multiple heap-based out-of-bounds WRITE vulnerabilities exist in parse_uname_string() (remoted_op.c). This function processes OS identification data from agents and contains a dangerous code pattern that appears in 4 locations within the same function: writing to strlen(ptr) - 1 without checking for empty strings. When the string is empty, strlen() returns 0, and 0 - 1 wraps to SIZE_MAX due to unsigned integer underflow. Due to pointer arithmetic wrapping, SIZE_MAX effectively becomes -1, causing a write exactly 1 byte before the allocated buffer. This corrupts heap metadata (e.g., the chunk size field in glibc malloc), leading to heap corruption. This issue has been patched in version 4.14.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Wazuh: Multiple Heap-based NULL WRITE Buffer Underflows in parse_uname_string()","id":"CVE-2026-41499","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wazuh:wazuh","products":["wazuh:wazuh"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"electerm has Command Injection Vulnerability via runMac function","id":"CVE-2026-41500"},"packages":[],"prev":{"headline":"Kimai: Team API Missing Object-Level Authorization","id":"CVE-2026-41498"},"products":["wazuh"],"published":"2026-04-29","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-29","vendors":["wazuh"]},"summary":"Attackers can trigger heap corruption via crafted agent data, potentially leading to code execution or service crashes in Wazuh.","url":"https://insights.sbomify.com/CVE-2026-41499/"}