CVE-2026-106705

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

GHSA-q45x-9wpf-qjgr ↗EUVD-2026-102904 ↗

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.
ELADMIN (eladmin-mp) n/a
ETK-2026-1791Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 11h 56msince last run
51mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+17h49m
0
+2h
+4h
+6h
+8h
+10h

description

ELADMIN (eladmin-mp) through version 2.7 has an authorization flaw in role-menu assignment. An authenticated non-administrative account delegated roles:edit can alter its own role's menu permissions and obtain capabilities beyond those intended.

mitigation

Remove or tightly limit roles:edit on non-administrative roles, and restrict access to role-management functions to trusted administrators. Review existing role and menu assignments for unauthorized changes.

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%14th percentile
agent run time
51m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 00:00Z
Δ 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 00:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-16 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1791",
  "cve_id": "CVE-2026-106705",
  "display_id": "CVE-2026-106705",
  "ghsa_id": "GHSA-q45x-9wpf-qjgr",
  "euvd_id": "EUVD-2026-102904",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization in ELADMIN role management",
  "summary": "ELADMIN (eladmin-mp) through version 2.7 has an authorization flaw in role-menu assignment. An authenticated non-administrative account delegated `roles:edit` can alter its own role's menu permissions and obtain capabilities beyond those intended.",
  "mitigation": "Remove or tightly limit `roles:edit` on non-administrative roles, and restrict access to role-management functions to trusted administrators. Review existing role and menu assignments for unauthorized changes.",
  "vendor": null,
  "product": "ELADMIN (eladmin-mp)",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0025,
  "epss_percentile": 0.1486,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 51.33384983333333,
  "t0_at": "2026-10-16T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T00:00:00+00:00",
      "url": "https://github.com/advisories/GHSA-q45x-9wpf-qjgr"
    }
  }
}

published 2026-10-16 16:57Z
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.