{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44901 exists.","fix":"No fix has been published for CVE-2026-44901 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44901 is a high-severity unsafe deserialization vulnerability in Wazuh Wazuh, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44901 and fix it if it is affected.\n\nWhat it is: CVE-2026-44901 is a high-severity unsafe deserialization vulnerability in Wazuh Wazuh, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44901 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-44901/ (Markdown: https://insights.sbomify.com/CVE-2026-44901/index.md)","id":"CVE-2026-44901","markdown":"https://insights.sbomify.com/CVE-2026-44901/index.md","name":"CVE-2026-44901","record":{"aliases":["GHSA-8c6v-7g3w-prrq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wazuh security platform","requires_auth":"high_privilege","summary":"A compromised cluster worker can trigger remote code execution as root on the Wazuh master node via unsafe deserialization in the DAPI protocol.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wazuh","vendor":"wazuh"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, AffectedItemsWazuhResult.merge() in framework/wazuh/core/results.py trusts the sort_casting field in a cluster worker's JSON response. During a distributed API merge, attacker-controlled type names are resolved through Python builtins without an allowlist. A compromised worker can set sort_casting to exec and place Python source in affected_items, causing the master to execute the payload as root when responses from multiple nodes are merged. 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":"weaponised"},"has_fix":false,"headline":"Wazuh Cluster DAPI Protocol Deserialization of Untrusted Data Remote Code Execution Vulnerability","id":"CVE-2026-44901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wazuh:wazuh","products":["wazuh:wazuh"],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"opentelemetry-js: Prometheus exporter process crash via malformed HTTP request","id":"CVE-2026-44902"},"packages":[],"prev":{"headline":"epa4all-client: VAU Signature bypass","id":"CVE-2026-44900"},"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["wazuh"]},"summary":"A compromised cluster worker can trigger remote code execution as root on the Wazuh master node via unsafe deserialization in the DAPI protocol.","url":"https://insights.sbomify.com/CVE-2026-44901/"}