CVE-2021-26814

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 8.7%, top 5% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 9%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
9%
EPSS %ILE
95%
KEV
Not listed

Published

March 6, 2021

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Aug 12, 2026
Patch available. Sources: github_release.
github_release Patch Available

Wazuh v4.0.4

Patch available: wazuh/wazuh v4.0.4

https://github.com/wazuh/wazuh/releases/tag/v4.0.4
generic

4.0.4 Release notes - Release notes · Wazuh documentation

https://documentation.wazuh.com/4.0/release-notes/release_4_0_4.html

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
wazuh—4.0.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-09-24 14:00 UTCEPSS rescore
  2. 2026-09-23 13:44 UTCEPSS rescore
  3. 2026-09-21 20:28 UTCEPSS rescore
  4. 2026-09-19 15:37 UTCEPSS rescore
  5. 2026-09-18 19:23 UTCEPSS rescore
  6. 2026-09-17 19:23 UTCEPSS rescore
  7. 2026-09-17 19:23 UTCEPSS rescore
  8. 2026-09-16 14:05 UTCEPSS rescore
  9. 2026-09-15 03:06 UTCEPSS rescore
  10. 2026-09-15 03:06 UTCEPSS rescore
  11. 2026-09-13 16:43 UTCEPSS rescore
  12. 2026-09-12 14:57 UTCEPSS rescore
  13. 2026-09-11 14:49 UTCEPSS rescore
  14. 2026-09-11 09:33 UTCEPSS rescore
  15. 2026-09-08 21:56 UTCEPSS rescore
  16. 2026-09-07 15:58 UTCEPSS rescore
  17. 2026-09-06 21:01 UTCOSV refresh
  18. 2026-09-06 13:44 UTCEPSS rescore
  19. 2026-09-05 15:25 UTCEPSS rescore
  20. 2026-09-04 13:57 UTCEPSS rescore
  21. 2026-09-04 05:03 UTCEPSS rescore
  22. 2026-09-04 05:03 UTCEPSS rescore
  23. 2026-09-02 14:08 UTCEPSS rescore
  24. 2026-09-01 13:50 UTCEPSS rescore
  25. 2026-09-01 03:32 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 19:14 UTCEPSS rescore
  2. 2026-08-30 01:19 UTCEPSS rescore
  3. 2026-08-28 21:37 UTCEPSS rescore
  4. 2026-08-27 14:22 UTCEPSS rescore
  5. 2026-08-26 14:42 UTCEPSS rescore
  6. 2026-08-25 13:45 UTCEPSS rescore
  7. 2026-08-24 14:12 UTCEPSS rescore
  8. 2026-08-23 00:16 UTCEPSS rescore
  9. 2026-08-21 23:46 UTCEPSS rescore
  10. 2026-08-20 22:52 UTCEPSS rescore
  11. 2026-08-20 06:55 UTCOSV refresh
  12. 2026-08-19 17:01 UTCEPSS rescore
  13. 2026-08-18 13:45 UTCEPSS rescore
  14. 2026-08-17 13:44 UTCEPSS rescore
  15. 2026-08-16 14:53 UTCEPSS rescore
  16. 2026-08-16 02:11 UTCEPSS rescore
  17. 2026-08-16 02:11 UTCEPSS rescore
  18. 2026-08-15 01:27 UTCEPSS rescore
  19. 2026-08-13 21:57 UTCEPSS rescore
  20. 2026-08-12 13:47 UTCEPSS rescore
  21. 2026-08-11 13:38 UTCEPSS rescore
  22. 2026-08-09 13:43 UTCEPSS rescore
  23. 2026-08-08 16:33 UTCEPSS rescore
  24. 2026-08-07 16:23 UTCEPSS rescore
  25. 2026-08-06 13:43 UTCEPSS rescore
  26. 2026-08-05 19:14 UTCEPSS rescore
  27. 2026-08-05 02:10 UTCOSV refresh
  28. 2026-08-04 15:06 UTCEPSS rescore
  29. 2026-08-04 10:34 UTCEPSS rescore
  30. 2026-08-03 10:33 UTCEPSS rescore
  31. 2026-08-02 02:24 UTCEPSS rescore
  32. 2026-08-01 04:13 UTCEPSS rescore
  33. 2026-07-30 16:25 UTCEPSS rescore
  34. 2026-07-30 16:25 UTCEPSS rescore
  35. 2026-07-30 01:28 UTCEPSS rescore
  36. 2026-07-30 01:27 UTCEPSS rescore
  37. 2026-07-28 15:33 UTCEPSS rescore
  38. 2026-07-25 14:15 UTCEPSS rescore
  39. 2026-07-24 14:15 UTCEPSS rescore
  40. 2026-07-23 14:16 UTCEPSS rescore
  41. 2026-07-23 01:58 UTCEG score recompute
  42. 2026-07-22 22:45 UTCEG score recompute
  43. 2026-07-22 14:06 UTCEPSS rescore
  44. 2026-07-22 14:06 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 17:05 UTCEPSS rescore
  48. 2026-07-19 14:28 UTCEPSS rescore
  49. 2026-07-19 02:27 UTCEPSS rescore
  50. 2026-07-19 02:27 UTCEPSS rescore
  51. 2026-07-19 00:29 UTCOSV refresh
  52. 2026-07-18 10:02 UTCEPSS rescore
  53. 2026-07-18 10:02 UTCEPSS rescore
  54. 2026-07-16 17:00 UTCEPSS rescore
  55. 2026-07-15 16:55 UTCEPSS rescore
  56. 2026-07-15 16:55 UTCEPSS rescore
  57. 2026-07-15 01:58 UTCEPSS rescore
  58. 2026-07-13 22:27 UTCEPSS rescore
  59. 2026-07-13 22:27 UTCEPSS rescore
  60. 2026-07-12 05:44 UTCEPSS rescore
  61. 2026-07-12 05:44 UTCEPSS rescore
  62. 2026-07-11 08:25 UTCEPSS rescore
  63. 2026-07-11 08:25 UTCEPSS rescore
  64. 2026-07-09 19:07 UTCEPSS rescore
  65. 2026-07-08 15:12 UTCEPSS rescore
  66. 2026-07-07 13:43 UTCEPSS rescore
  67. 2026-07-06 16:25 UTCEPSS rescore
  68. 2026-07-06 16:25 UTCEPSS rescore
  69. 2026-07-06 02:21 UTCEPSS rescore
  70. 2026-07-06 02:21 UTCEPSS rescore
  71. 2026-07-05 02:28 UTCEPSS rescore
  72. 2026-07-04 06:29 UTCEPSS rescore
  73. 2026-07-04 06:29 UTCEPSS rescore
  74. 2026-07-02 16:57 UTCEPSS rescore
  75. 2026-07-01 15:03 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCCYS4srl/CVE-2021-26814
    First seen May 18, 2021

    PoC of CVE-2021-26814

    Open source ↗
  • GitHub PoCWickdDavid/CVE-2021-26814
    First seen May 17, 2021

    A simple python PoC to exploit CVE-2021-26814 and gain RCE on Wazuh Manager (v.4.0.0-4.0.3) through the API service.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2021-26814?
CVE-2021-26814 is a high vulnerability published on March 6, 2021. 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…
When was CVE-2021-26814 disclosed?
CVE-2021-26814 was first published in the National Vulnerability Database on March 6, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-26814 actively exploited?
CVE-2021-26814 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9% probability of exploitation in the next 30 days, which ranks it in the top 5.0% of all scored CVEs.
What is the CVSS score of CVE-2021-26814?
CVE-2021-26814 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2021-26814?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-26814, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-26814

Explore →

Is Your Infrastructure Affected by CVE-2021-26814?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs