CVE-2026-86008

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

GHSA-9pv5-rm76-3qwj ↗EUVD-2026-102921 ↗

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.
Mailu
fixed in master
CWE-285 Improper Authorization
ETK-2026-1818Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 06h 08msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+31h19m
0
+2h
+4h
+6h
+8h
+10h

description

Mailu deployments built before the corrective commit are affected by an authorization flaw in account-management actions. A domain manager may be able to assume a more privileged account by resetting its credentials or obtaining its tokens; this requires an existing domain-manager account and a higher-privileged target account.

mitigation

Update Mailu to a current master build that includes commit 8577c929b4ade04d3cd4210cf036601abd793556. Until updated, restrict domain-manager access and review privileged-account credentials and active tokens.

fixed in master

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.31%22nd percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 16:16Z
Δ 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-16 16:16Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1818",
  "cve_id": "CVE-2026-86008",
  "display_id": "CVE-2026-86008",
  "ghsa_id": "GHSA-9pv5-rm76-3qwj",
  "euvd_id": "EUVD-2026-102921",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization in Mailu account management",
  "summary": "Mailu deployments built before the corrective commit are affected by an authorization flaw in account-management actions. A domain manager may be able to assume a more privileged account by resetting its credentials or obtaining its tokens; this requires an existing domain-manager account and a higher-privileged target account.",
  "mitigation": "Update Mailu to a current master build that includes commit 8577c929b4ade04d3cd4210cf036601abd793556. Until updated, restrict domain-manager access and review privileged-account credentials and active tokens.",
  "vendor": "Mailu",
  "product": "Mailu",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 8577c929b4ade04d3cd4210cf036601abd793556"
      ],
      "ecosystem": "mailu",
      "fixed_versions": [
        "master"
      ],
      "package_name": "Mailu",
      "purl": null
    }
  ],
  "cwes": [
    285
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2286,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.310706333333332,
  "t0_at": "2026-10-16T16:16:51.097000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T16:16:51.097000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T16:16:51.097000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-86008"
    }
  }
}

published 2026-10-16 22:50Z
last change 2026-10-21 04:45Z

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.