Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Improper Input Validation (RCE)GHSA-w36g-q975-37rg

HIGH

GHSA-w36g-q975-37rg is a high-severity (CVSS 8.8) Path Traversal vulnerability in wazuh. 2 public exploit references exist, so weaponization risk is real. A fix is available for wazuh — see the affected versions and patch details below.

Also known asCVE-2021-26814
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
8.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk
0.00%26.9%53.7%80.6%64.0%8.7%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-w36g-q975-37rg by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
wazuhnpm
54downloads / week

Description

Wazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/files URI. An authenticated user to the service may exploit incomplete input validation on the /manager/files API to inject arbitrary code within the API service script.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmwazuh≥ 4.0.0&&< 4.0.44.0.4npm install wazuh@4.0.4

Affected Products

1 product · 1 configurations
Application
wazuhwazuh
≥ 4.0.0 && ≤ 4.0.3
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Wazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to exe…

github.comGithubMay 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wazuh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update wazuh to 4.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w36g-q975-37rg is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Wazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/files URI. An authenticated user to the service may exploit incomplete input validation on the /manager/files API to inject arbitrary code within the API service script.
O3 Security · Impact-Aware SCA

Is GHSA-w36g-q975-37rg in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Input Validation (RCE) (High 8.8)