{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62788 exists.","fix":"No fix has been published for CVE-2025-62788 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62788 is a medium-severity use after free vulnerability in Wazuh Wazuh, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62788 and fix it if it is affected.\n\nWhat it is: CVE-2025-62788 is a medium-severity use after free vulnerability in Wazuh Wazuh, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62788 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-2025-62788/ (Markdown: https://insights.sbomify.com/CVE-2025-62788/index.md)","id":"CVE-2025-62788","markdown":"https://insights.sbomify.com/CVE-2025-62788/index.md","name":"CVE-2025-62788","record":{"aliases":["GHSA-qjcw-fjvh-8q4g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Wazuh security platform","requires_auth":"none","summary":"A compromised agent can corrupt application integrity or cause denial of service in the Wazuh manager via a use-after-free vulnerability in event logging.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wazuh","vendor":"wazuh"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to 4.11.0, w_copy_event_for_log() references memory (initially allocated in OS_CleanMSG()) after it has been freed. A compromised agent can potentially compromise the integrity of the application by sending a specially crafted message to the wazuh manager. An attacker who is able to craft and send an agent message to the wazuh manager can leverage this issue to potentially compromise the integrity of the application (the use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere). This vulnerability is fixed in 4.11.0.","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 Vulnerable to Heap Use After Free in w_copy_event_for_log","id":"CVE-2025-62788","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wazuh:wazuh","products":["wazuh:wazuh"],"type":"use_after_free","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Wazuh vulnerable to NULL pointer dereference in fim_alert line 712","id":"CVE-2025-62789"},"packages":[],"prev":{"headline":"Wazuh Vulnerable to Heap-based Buffer Over-read in DecodeWinevt","id":"CVE-2025-62787"},"products":["wazuh"],"published":"2025-10-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":"2025-10-29","vendors":["wazuh"]},"summary":"A compromised agent can corrupt application integrity or cause denial of service in the Wazuh manager via a use-after-free vulnerability in event logging.","url":"https://insights.sbomify.com/CVE-2025-62788/"}