CVE-2026-94380

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

GHSA-qh9j-c6pq-98xh ↗EUVD-2026-109777 ↗

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.
HAVELSAN Inc. Liman MYS >= 2.3.4-1124, < 2.3.5-1131
fixed in 2.3.5-1131
CWE-640 Weak Password Recovery Mechanism for Forgotten Password
ETK-2026-2645Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 41msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h02m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Liman MYS versions 2.3.4-1124 through before 2.3.5-1131 have an insecure forgotten-password recovery process. An attacker may be able to abuse the recovery function; the advisory does not specify additional preconditions.

mitigation

Upgrade Liman MYS to version 2.3.5-1131 or later. Until the update is deployed, restrict access to the password-recovery interface to reduce exposure.

fixed in 2.3.5-1131

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 11:15Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-26 11:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2645",
  "cve_id": "CVE-2026-94380",
  "display_id": "CVE-2026-94380",
  "ghsa_id": "GHSA-qh9j-c6pq-98xh",
  "euvd_id": "EUVD-2026-109777",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Password recovery weakness in Liman MYS",
  "summary": "Liman MYS versions 2.3.4-1124 through before 2.3.5-1131 have an insecure forgotten-password recovery process. An attacker may be able to abuse the recovery function; the advisory does not specify additional preconditions.",
  "mitigation": "Upgrade Liman MYS to version 2.3.5-1131 or later. Until the update is deployed, restrict access to the password-recovery interface to reduce exposure.",
  "vendor": "HAVELSAN Inc.",
  "product": "Liman MYS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.3.4-1124, < 2.3.5-1131"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.3.5-1131"
      ],
      "package_name": "Liman MYS",
      "purl": null
    }
  ],
  "cwes": [
    640
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.18842838333333,
  "t0_at": "2026-10-26T11:15:45.141000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T11:15:45.141000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T11:15:45.141000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94380"
    }
  }
}

published 2026-10-26 11:42Z
last change 2026-10-26 16:24Z

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.