CVE-2025-34294Public exploit

Rejected report involving example threat-removal script

Published Oct 28, 2025 · Updated Oct 28, 2025

Wazuh is not an affected product under CVE-2025-34294 because the reported behavior comes from a documentation-published example script. The optional Windows remove-threat script records Active Response status before deleting a path, enabling an oplock and link-redirection race against the deletion target. Only Windows agents with an automatic threat-removal integration based on that example expose the described arbitrary deletion and privilege-escalation chain; the CNA rejected the CVE and removed its product claim.

CVSS severity7.1
High
EPSS probabilityUnavailable
No score available in this record
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Wazuh is not an affected product under CVE-2025-34294 because the reported behavior comes from a documentation-published example script. The optional Windows remove-threat script records Active Response status before deleting a path, enabling an oplock and link-redirection race against the deletion target. Only Windows agents with an automatic threat-removal integration based on that example expose the described arbitrary deletion and privilege-escalation chain; the CNA rejected the CVE and removed its product claim.

The record

CVE
CVE-2025-34294
Published
Oct 28, 2025
Updated
Oct 28, 2025
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-367, CWE-59, T1068
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Oct 28, 2025CVE publishedPublication date reported by the CVE source.
  2. Oct 28, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Wazuh · Wazuhversion=0

Published CVSS scores

7.1GitHub Security AdvisoryCVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
CWE-59Improper Link Resolution Before File Access ('Link Following')
T1068Exploitation for Privilege Escalation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo