CVE-2026-45798

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% 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, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.5.0 until 4.14.6 and 5.0.0-beta2, compare_wazuh_versions() in src/shared/version_op.c copies the attacker-controlled enrollment V: field into a 10-byte stack buffer with strncpy() but does not explicitly terminate the buffer. The function is reachable before authentication through wazuh-authd on TCP port 1515 when anonymous TLS enrollment is enabled. A version string of at least nine non-null bytes can cause strchr() and strtok() to read beyond ver2 and can make strtok() write a null byte into adjacent stack memory, allowing a remote denial of service. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 19, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

Wazuh v5.0.0 Beta 2

Patch available: wazuh/wazuh v5.0.0-beta2 (pre-release)

https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta2
github_release Patch Available

Wazuh v4.14.6

Patch available: wazuh/wazuh v4.14.6

https://github.com/wazuh/wazuh/releases/tag/v4.14.6
github_commit Patch Available

commit b6aac379982d (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta2 (contains commit b6aac379982d)

https://github.com/wazuh/wazuh/commit/b6aac379982d6144b8da38450cbea6c8dc15be44
github_pr Patch Available

Fix string handling in version comparison function

Patch available: wazuh/wazuh v5.0.0-beta2 (PR #36059 merged 2026-05-13)

https://github.com/wazuh/wazuh/pull/36059
github Patch Available

Pre-auth stack-buffer-overflow in compare_wazuh_versions reachable from wazuh-authd (TCP/1515) via crafted enrollment V: field · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-4fvp-jfc3-qr6r

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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.

  1. 2026-08-25 20:59 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 20:32 UTCEG score recompute
  4. 2026-08-23 07:50 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 07:24 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 06:58 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 06:32 UTCEG score recompute
  11. 2026-08-19 18:18 UTCEG score recompute
  12. 2026-08-19 17:23 UTCEG score recompute
  13. 2026-08-19 16:22 UTCEG score recompute
  14. 2026-08-19 16:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-45798?
CVE-2026-45798 is a high vulnerability published on August 19, 2026. Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.5.0 until 4.14.6 and 5.0.0-beta2, comparewazuhversions() in src/shared/version_op.c copies the attacker-controlled enrollment V: field into a 10-byte stack buffer with strncpy() but does not…
When was CVE-2026-45798 disclosed?
CVE-2026-45798 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45798 actively exploited?
CVE-2026-45798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.6% of all scored CVEs.
What is the CVSS score of CVE-2026-45798?
CVE-2026-45798 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45798, 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

Explore the affected products and dependency analysis for CVE-2026-45798

Explore →

Is Your Infrastructure Affected by CVE-2026-45798?

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

Start Free Scan →Browse All CVEs