CVE-2026-74040

waiting for further signalsZero needs more public information before it can validate it.

GHSA-88p6-7cm8-xwj8 ↗EUVD-2026-98676 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Wazuh wazuh-manager >= 3.9.0
fixed in 4.14.8
CWE-862 Missing Authorization
ETK-2026-1470Zero's internal tracking ID, independent of the CVE number., permanent identifier
6d 13h 57msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+26h22m
0
+2h
+4h
+6h
+8h
+10h

description

Wazuh wazuh-manager versions 3.9.0 through versions earlier than 4.14.8 allow protected manager files to be overwritten through cluster file handling. An attacker who has control of a cluster worker could use this to run code with root privileges on the manager and affect managed agents.

mitigation

Upgrade wazuh-manager to version 4.14.8 or later. Until upgrades are complete, restrict cluster-worker control and access to trusted administrators and systems.

fixed in 4.14.8

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.55%45th percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 13:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-13 13:27Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-74040

{
  "etk_id": "ETK-2026-1470",
  "cve_id": "CVE-2026-74040",
  "display_id": "CVE-2026-74040",
  "ghsa_id": "GHSA-88p6-7cm8-xwj8",
  "euvd_id": "EUVD-2026-98676",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file overwrite in Wazuh manager cluster handling",
  "summary": "Wazuh wazuh-manager versions 3.9.0 through versions earlier than 4.14.8 allow protected manager files to be overwritten through cluster file handling. An attacker who has control of a cluster worker could use this to run code with root privileges on the manager and affect managed agents.",
  "mitigation": "Upgrade wazuh-manager to version 4.14.8 or later. Until upgrades are complete, restrict cluster-worker control and access to trusted administrators and systems.",
  "vendor": "Wazuh",
  "product": "wazuh-manager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.9.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.14.8"
      ],
      "package_name": "wazuh-manager",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 9.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
  "epss_score": 0.0055,
  "epss_percentile": 0.4504,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.5658148,
  "t0_at": "2026-10-13T13:27:30.557000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T13:27:30.557000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T13:27:30.557000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74040"
    }
  }
}

published 2026-10-13 14:35Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.