CVE-2026-48162 json
Wazuh: cluster peer can read arbitrary master files and forge offline REST API administrator tokens via DAPI tmp_file path injection in Wazuh manager
published 3mo ago modified 16d ago also EUVD-2026-62556 , GHSA-r6f5-h662-8ffc
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository wazuh/wazuh. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wazuh wazuh 4.14.6, 5.0.0-beta3
- github.com/wazuh/wazuh@de1eeed commit
- github.com/wazuh/wazuh#36246 pull request
- github.com/wazuh/wazuh/releases/tag/v4.14.6 release
- github.com/wazuh/wazuh/releases/tag/v5.0.0-beta3 release
Is CVE-2026-48162 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/wazuh/wazuh/security/advisories/GHSA-r6f5-h662-8ffc referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected products
- wazuh wazuh
Classification
- Weakness
-
- CWE-73 External Control of File Name or Path
References
-
github.com
/wazuh/wazuh/pull/36246
issue-tracking, patch
-
github.com
/wazuh/wazuh/commit/de1eeedbe336744934be4e20d87d84a76e438cee
patch
-
github.com
/wazuh/wazuh/releases/tag/v4.14.6
patch, release-notes
-
github.com
/wazuh/wazuh/releases/tag/v5.0.0-beta3
patch, release-notes
-
github.com
/wazuh/wazuh/security/advisories/GHSA-r6f5-h662-8ffc
exploit, vendor-advisory, advisory
Sources
- CVE List CVE-2026-48162
- NVD CVE-2026-48162
- Maintainer advisory GHSA-r6f5-h662-8ffc
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of wazuh/wazuh published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.