CVE-2026-74034

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Elevated

Also known asEUVD-2026-98672 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Wazuh from 4.1.0 before 4.14.8 contains a missing origin check in wm_agent_upgrade that allows enrolled agents to issue upgrade_custom commands with attacker-controlled file_path. Attackers can inject an upgrade_custom message over the agent channel to read arbitrary files as root, exfiltrating /etc/shadow and client.keys.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 13, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Oct 13, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_release.
Web page

Wazuh 4.1.0 before 4.14.8 Arbitrary File Read via upgrade_custom Command | Advisories | VulnCheck

https://www.vulncheck.com/advisories/wazuh-4.1.0-before-4.14.8-arbitrary-file-read-via-upgrade-custom-command
GitHub release Patch Available

Wazuh v4.14.8

Patch available: wazuh/wazuh v4.14.8

https://github.com/wazuh/wazuh/releases/tag/v4.14.8
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Arbitrary file read as root via agent-injected upgrade_custom command · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-r7hm-43xr-477j

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-03 03:03 UTCEG score recompute
  3. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-26 15:05 UTCEG score recompute
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-25 14:04 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-22 11:32 UTCEG score recompute
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-19 16:38 UTCEG score recompute
  21. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  23. 2026-10-18 03:14 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 8 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-15 16:09 UTCEG score recompute
  3. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-14 14:38 UTCEG score recompute
  5. 2026-10-14 14:18 UTCEG score recompute
  6. 2026-10-13 14:28 UTCEG score recompute
  7. 2026-10-13 13:41 UTCEG score recomputeFirst assessed: 7.5 HIGH
  8. 2026-10-13 13:39 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCroninreilly/wazuh-unauth-chain
    Published Oct 14, 2026

    Wazuh PoC chaining CVE-2026-74034 file read and CVE-2026-74041 command execution; fixed in 4.14.8. Python standard library only.

    Open source ↗

Frequently asked(5)

What is CVE-2026-74034?
CVE-2026-74034 is a high-severity vulnerability; its CVE record was published on October 13, 2026. Wazuh from 4.1.0 before 4.14.8 contains a missing origin check in wm_agent_upgrade that allows enrolled agents to issue upgrade_custom commands with attacker-controlled file_path. Attackers can inject an upgrade_custom message over the agent channel to read arbitrary files as root, exfiltrating…
When was CVE-2026-74034 made public?
CVE-2026-74034 was made public on October 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 13, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-74034 actively exploited?
CVE-2026-74034 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74034?
CVE-2026-74034 has a CVSS base score of 7.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-74034?
A fix for CVE-2026-74034 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-74034?

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