CVE-2026-91844

validatedZero produced an exploit or a check.

GHSA-rg38-3cv4-mj9c ↗EUVD-2026-94982 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
İzometri IT Services Domestic and Foreign Trade Co. Ltd. eimzamip >= v1.6.4, < v1.6.6
fixed in v1.6.6
CWE-434 Unrestricted Upload of File with Dangerous Type
ETK-2026-1054Zero's internal tracking ID, independent of the CVE number., permanent identifier
+17h12mTTV
22mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+17h12magent stopped
0
+6h
+12h

description

eimzamip versions 1.6.4 through before 1.6.6 are affected by unrestricted upload of dangerous file types. An attacker who can access the upload feature may submit malicious files.

mitigation

Upgrade eimzamip to v1.6.6 or later.

fixed in v1.6.6

check
available
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.20%9th percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 13:42Z
Δ 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 check: a technique exists and was validated, 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-08 13:42Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1054",
  "cve_id": "CVE-2026-91844",
  "display_id": "CVE-2026-91844",
  "ghsa_id": "GHSA-rg38-3cv4-mj9c",
  "euvd_id": "EUVD-2026-94982",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Dangerous file upload in eimzamip",
  "summary": "eimzamip versions 1.6.4 through before 1.6.6 are affected by unrestricted upload of dangerous file types. An attacker who can access the upload feature may submit malicious files.",
  "mitigation": "Upgrade eimzamip to v1.6.6 or later.",
  "vendor": "İzometri IT Services Domestic and Foreign Trade Co. Ltd.",
  "product": "eimzamip",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= v1.6.4, < v1.6.6"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "v1.6.6"
      ],
      "package_name": "eimzamip",
      "purl": null
    }
  ],
  "cwes": [
    434
  ],
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
  "epss_score": 0.002,
  "epss_percentile": 0.0918,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 22.328515183333334,
  "t0_at": "2026-10-08T13:42:27.448000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-09T06:54:52.704850+00:00",
      "days": 0.7169589913194444,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T13:42:27.448000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-08T13:42:27.448000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T13:42:27.448000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-91844"
    }
  }
}

published 2026-10-09 06:32Z
last change 2026-10-21 21:36Z

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.