Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
No reference.
Fri, 19 Dec 2025 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-367 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Fri, 19 Dec 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Wazuh File Integrity Monitoring (FIM) & Active Response Arbitrary File Deletion as SYSTEM | |
| Metrics |
ssvc
|
Fri, 19 Dec 2025 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Wazuh's File Integrity Monitoring (FIM), when configured with automatic threat removal, contains a time-of-check/time-of-use (TOCTOU) race condition that can allow a local, low-privileged attacker to cause the Wazuh service (running as NT AUTHORITY\SYSTEM) to delete attacker-controlled files or paths. The root cause is insufficient synchronization and lack of robust final-path validation in the threat-removal workflow: the agent records an active-response action and proceeds to perform deletion without guaranteeing the deletion target is the originally intended file. This can result in SYSTEM-level arbitrary file or folder deletion and consequent local privilege escalation. Wazuh made an attempted fix via pull request 8697 on 2025-07-10, but that change was incomplete. | 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. |
| CPEs | ||
| Metrics |
cvssV4_0
|
cvssV4_0
|
Wed, 19 Nov 2025 01:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:* |
Wed, 29 Oct 2025 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wazuh
Wazuh wazuh |
|
| Vendors & Products |
Wazuh
Wazuh wazuh |
Tue, 28 Oct 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 28 Oct 2025 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Wazuh's File Integrity Monitoring (FIM), when configured with automatic threat removal, contains a time-of-check/time-of-use (TOCTOU) race condition that can allow a local, low-privileged attacker to cause the Wazuh service (running as NT AUTHORITY\SYSTEM) to delete attacker-controlled files or paths. The root cause is insufficient synchronization and lack of robust final-path validation in the threat-removal workflow: the agent records an active-response action and proceeds to perform deletion without guaranteeing the deletion target is the originally intended file. This can result in SYSTEM-level arbitrary file or folder deletion and consequent local privilege escalation. Wazuh made an attempted fix via pull request 8697 on 2025-07-10, but that change was incomplete. | |
| Title | Wazuh File Integrity Monitoring (FIM) & Active Response Arbitrary File Deletion as SYSTEM | |
| Weaknesses | CWE-367 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: REJECTED
Assigner: VulnCheck
Published:
Updated: 2025-12-19T14:24:12.863Z
Reserved: 2025-04-15T19:15:22.581Z
Link: CVE-2025-34294
Updated:
Status : Rejected
Published: 2025-10-28T16:15:37.167
Modified: 2025-12-19T15:15:55.860
Link: CVE-2025-34294
No data.
OpenCVE Enrichment
Updated: 2025-10-29T10:57:54Z
No weakness.