CVE-2026-89292

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

EUVD-2026-115727 ↗

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.
Eclipse Foundation Eclipse Mnestix >= 1.6.0, < 2.3.0
fixed in 2.3.0
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-3356Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 05msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h06m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Eclipse Mnestix Browser versions 1.6.0 through 2.2.x can expose the MNESTIX_BACKEND_API_KEY for configured infrastructures. An unauthenticated attacker who can reach an affected instance may exfiltrate those keys.

mitigation

Upgrade Eclipse Mnestix to version 2.3.0 or later. Restrict network access to affected Browser instances until the upgrade is complete.

fixed in 2.3.0

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.
–
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
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 09:31Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-03 09:31Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3356",
  "cve_id": "CVE-2026-89292",
  "display_id": "CVE-2026-89292",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-115727",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SSRF in Eclipse Mnestix Browser",
  "summary": "Eclipse Mnestix Browser versions 1.6.0 through 2.2.x can expose the MNESTIX_BACKEND_API_KEY for configured infrastructures. An unauthenticated attacker who can reach an affected instance may exfiltrate those keys.",
  "mitigation": "Upgrade Eclipse Mnestix to version 2.3.0 or later. Restrict network access to affected Browser instances until the upgrade is complete.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse Mnestix",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.6.0, < 2.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.3.0"
      ],
      "package_name": "Eclipse Mnestix",
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 39.060795283333334,
  "t0_at": "2026-11-03T09:31:27.136000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T09:31:27.136000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T09:31:27.136000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-89292"
    }
  }
}

published 2026-11-03 09:58Z
last change 2026-11-03 12:07Z

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.