{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25772 exists.","fix":"No fix has been published for CVE-2026-25772 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25772 is a medium-severity vulnerability in Wazuh Wazuh, published on 17 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25772 and fix it if it is affected.\n\nWhat it is: CVE-2026-25772 is a medium-severity vulnerability in Wazuh Wazuh, published on 17 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25772 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-25772/ (Markdown: https://insights.sbomify.com/CVE-2026-25772/index.md)","id":"CVE-2026-25772","markdown":"https://insights.sbomify.com/CVE-2026-25772/index.md","name":"CVE-2026-25772","record":{"aliases":["GHSA-h7vp-j34v-h6j5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wazuh security platform","requires_auth":"high_privilege","summary":"An integer underflow in Wazuh's database synchronization allows stack corruption, leading to denial of service or remote code execution.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wazuh","vendor":"wazuh"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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-121","name":"Stack-based Buffer Overflow"}],"description":"Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0 and prior to version 4.14.3, a stack-based buffer overflow vulnerability exists in the Wazuh Database synchronization module (`wdb_delta_event.c`). The SQL query construction logic allows for an integer underflow when calculating the remaining buffer size. This occurs because the code incorrectly aggregates the return value of `snprintf`. If a specific database synchronization payload exceeds the size of the query buffer (2048 bytes), the size calculation wraps around to a massive integer, effectively removing bounds checking for subsequent writes. This allows an attacker to corrupt the stack, leading to a Denial of Service (DoS) or potentially RCE. Version 4.14.3 fixes the issue.","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 Database Synchronization Vulnerable to Stack-based Buffer Overflow via snprintf Integer Underflow","id":"CVE-2026-25772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wazuh:wazuh","products":["wazuh:wazuh"],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Focalboard doesn't sanitize category IDs before incorporating them into dynamic SQL statements","id":"CVE-2026-25773"},"packages":[],"prev":{"headline":"Wazuh Vulnerable to Denial of Service via Synchronous I/O Blocking in Asynchronous Authentication Middleware","id":"CVE-2026-25771"},"products":["wazuh"],"published":"2026-03-17","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-03-17","vendors":["wazuh"]},"summary":"An integer underflow in Wazuh's database synchronization allows stack corruption, leading to denial of service or remote code execution.","url":"https://insights.sbomify.com/CVE-2026-25772/"}