CVE-2025-34294 Details
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as the behavior originates from a documentation-published Active Response example script. Please refer to this advisory ( https://github.com/wazuh/wazuh-documentation/security/advisories/GHSA-46r5-xp98-fpgg ) for further information.
A time-of-check/time-of-use (TOCTOU) race condition vulnerability has been identified in Wazuh's File Integrity Monitoring (FIM) component. This issue arises when FIM is configured to automatically remove threats. The vulnerability allows a local, low-privileged attacker to manipulate the Wazuh service, which runs under the NT AUTHORITY\SYSTEM account, into deleting files or directories controlled by the attacker. The problem stems from inadequate synchronization and a lack of thorough validation of the final deletion path in the threat-removal process. As a result, the agent may delete a file that was not originally intended, leading to unauthorized deletion of files or folders at the SYSTEM level and potential local privilege escalation.
Users can disable the automatic threat removal feature in Wazuh's File Integrity Monitoring settings to prevent exploitation of this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No CVSS 3.x data is available for this CVE.
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
No references are available for this CVE.
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
No affected product data is available for this CVE.
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Dec 19, 2025 | CVE Rejected | [email protected] |
| Dec 19, 2025 | CVE Modified | [email protected] |
| Oct 28, 2025 | New CVE Received | [email protected] |