Wazuh 4.14.3 before 4.14.8 contains a case-sensitivity mismatch between the ossec.conf validator and wazuh-logcollector that bypasses remote-command validation. Authenticated users with manager:update_config can inject an uppercase LOG_FORMAT command localfile that the collector runs as root on reload.
CVE-2026-74041
CRITICALPre-NVD 9.19.1
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALlow confidence
- EG Risk
- 41EG Risk 41/100
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 (value × EchelonGraph’s weight)Severity91% × 45%The EG Score, 9.1 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 13, 2026
Advisory Details (3)
Auto-updated Oct 13, 2026🔬 Proof of concept available. Patch available. Sources: github, github_release.
Web page
Wazuh 4.14.3 before 4.14.8 Remote Command Validation Bypass via Case Mismatch | Advisories | VulnCheck
https://www.vulncheck.com/advisories/wazuh-4.14.3-before-4.14.8-remote-command-validation-bypass-via-case-mismatchGitHub release Patch Available
Wazuh v4.14.8
Patch available: wazuh/wazuh v4.14.8
https://github.com/wazuh/wazuh/releases/tag/v4.14.8GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Case-sensitivity mismatch bypasses remote-command validation, allowing command execution as root · Advisory · wazuh/wazuh · GitHub
https://github.com/wazuh/wazuh/security/advisories/GHSA-cjf8-wjx6-hjw6Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-10-13 14:27 UTCEG score recompute
- 2026-10-13 13:41 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
- 2026-10-13 13:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-74041?
CVE-2026-74041 is a critical-severity vulnerability; its CVE record was published on October 13, 2026. Wazuh 4.14.3 before 4.14.8 contains a case-sensitivity mismatch between the ossec.conf validator and wazuh-logcollector that bypasses remote-command validation. Authenticated users with manager:updateconfig can inject an uppercase LOGFORMAT command localfile that the collector runs as root on…
When was CVE-2026-74041 made public?
CVE-2026-74041 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 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-74041?
CVE-2026-74041 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-74041?
A fix for CVE-2026-74041 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-74041
Is Your Infrastructure Affected by CVE-2026-74041?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.