dbcve.org
CWE-73Weakness · CWE-73

CVE-2026-48162

CRITICAL · 9.1 CVSS v3.1 Published 2026-08-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 5 days old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix High confidence

Upgrade to Wazuh 4.14.6 (stable 4.x) or 5.0.0+ (stable 5.x branch)

  1. 1. Identify current Wazuh installation version by running: cat /var/ossec/etc/ossec.conf | grep '<version>' or check package manager: rpm -qi wazuh-manager or dpkg -l wazuh-manager
  2. 2. If running version 4.0.0 through 4.14.5, plan upgrade to version 4.14.6
  3. 3. If running version 5.0.0-beta3, upgrade to stable 5.0.0 or later release
  4. 4. Before upgrading, backup configuration: cp -r /var/ossec/etc /var/ossec_backup_$(date +%Y%m%d)
  5. 5. Upgrade Wazuh manager using official documentation: https://documentation.wazuh.com/current/upgrade-guide/index.html
  6. 6. After upgrade, verify the fix by confirming the vulnerable code no longer exists in framework/wazuh/core/cluster/dapi/dapi.py
  7. 7. Regenerate the REST API private key as a precaution: rm /var/ossec/api/configuration/security/private_key.pem && /var/ossec/bin/wazuh-apid_db.sh (or restart Wazuh API service)
Caveat Minor: API private key will be regenerated on first restart after upgrade; any existing stored API tokens will need to be re-issued

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $4,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48162 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data