EUVD-2026-62556Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Attacker must hold the shared cluster key (PR:H) but acts over the network with low complexity; arbitrary file read yields the API key, escaping the DAPI component to compromise the security authority (S:C), giving full C/I/A via forged admin tokens.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta3, DistributedAPI.send_tmp_file() in framework/wazuh/core/cluster/dapi/dapi.py joins an attacker-controlled tmp_file value to WAZUH_PATH without canonicalization or confinement. A cluster peer holding the shared Fernet key can use traversal or an absolute path to make the master return any readable file over the cluster channel. Reading /var/ossec/api/configuration/security/private_key.pem allows the peer to forge administrator REST API tokens offline and then exercise administrative privileges without creating an account. This issue is fixed in versions 4.14.6 and 5.0.0-beta3.
AnalysisAI
Arbitrary file read in Wazuh cluster deployments (4.0.0 through 4.14.5, and 5.0.0-beta1/beta2) lets a peer node that already holds the shared cluster Fernet key coerce the master into returning any file it can read over the encrypted cluster channel. By retrieving /var/ossec/api/configuration/security/private_key.pem, that peer can forge administrator REST API tokens offline and exercise full administrative privileges without ever creating an account. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires the attacker to be an authenticated cluster peer that possesses the shared cluster Fernet key (CVSS PR:H) and can reach the master over the cluster channel - i.e. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The 9.1 CVSS base score looks critical, but the real-world barrier is meaningful: the CVSS vector encodes PR:H, and the description confirms the attacker must already be a cluster peer holding the shared Fernet key - so this is a privilege-escalation / lateral-movement primitive available to a compromised or rogue worker node, not an internet-facing unauthenticated RCE. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has compromised a single Wazuh worker node (or a malicious insider operating one) recovers the shared cluster Fernet key and issues a DAPI send_tmp_file request with tmp_file set to '/var/ossec/api/configuration/security/private_key.pem', causing the master to return the API signing key over the cluster channel. Using that key offline, the attacker mints a valid administrator REST API JWT and drives full administrative operations against the manager without creating any account. … |
| Remediation | Vendor-released patch: upgrade to Wazuh 4.14.6 (https://github.com/wazuh/wazuh/releases/tag/v4.14.6) on the 4.x line, or to 5.0.0-beta3 (https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3) if running the 5.0 pre-release; the fix (PR https://github.com/wazuh/wazuh/pull/36246, commit de1eeedbe336744934be4e20d87d84a76e438cee) adds realpath resolution and confinement of tmp_file to the OSSEC tmp directory. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, conduct a comprehensive inventory of all Wazuh deployments to identify instances running versions 4.0.0-4.14.5 or 5.0.0-beta1/beta2. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl comman
A critical deserialization vulnerability in Wazuh's cluster mode allows attackers with access to any worker node to achi
The agent in OSSEC through 3.1.0 on Windows allows local users to gain NT AUTHORITY\SYSTEM access via Directory Traversa
CVE-2024-1243 is an improper input validation vulnerability in Wazuh agent for Windows (versions prior to 4.8.0) that al
Wazuh Manager in Wazuh through 4.1.5 is affected by a remote Integer Underflow vulnerability that might lead to denial o
NDJSON injection in Wazuh Manager before 5.0.0-beta3 lets any enrolled agent smuggle arbitrary OpenSearch bulk operation
Wazuh is a free and open source platform used for threat prevention, detection, and response. Rated critical severity (C
Authenticated remote code execution in Wazuh's Cluster Distributed API (DAPI) lets any peer holding the shared cluster k
Privilege escalation in Wazuh Manager versions 3.9.0 through 4.14.2 allows authenticated cluster nodes to achieve unauth
Path-traversal-driven remote code execution in Wazuh 4.3.0 through 4.14.5 (and 5.0.0-beta1/beta2) lets a cluster peer th
Path-traversal-driven root code execution affects the Wazuh security platform's cluster synchronization layer in version
Same weakness CWE-73 – External Control of File Name or Path
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today