Skip to main content

Eclipse Mnestix Browser EUVDEUVD-2026-115727

| CVE-2026-89292 CRITICAL
Server-Side Request Forgery (SSRF) (CWE-918)
2026-11-03 eclipse GHSA-c7g8-f337-8fr6
9.2
CVSS 4.0 · Vendor: eclipse
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed Mnestix Browser over network
  2. Exploit
    Send crafted SSRF request
  3. Execution
    Exfiltrate MNESTIX_BACKEND_API_KEY for all Infrastructures
  4. Impact
    Authenticate to backend infrastructures with stolen key

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must have network access to a running Eclipse Mnestix Browser instance at version 1.6.0 through any release before 2.3.0 that has one or more Infrastructures configured with a MNESTIX_BACKEND_API_KEY - the keys being exfiltrated must exist in the deployment. Per the CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:N) no authentication, no special attack requirement, and no user interaction are needed against affected versions, so the primary limiting factors are reachability of the instance over the network and the affected version range; the specific SSRF trigger (which endpoint or parameter is abused) is not described in the available sources.

Impact

Multiple signals align toward genuine priority despite incomplete telemetry. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, low-complexity, unauthenticated exploitation with high confidentiality impact on both the vulnerable system (VC:H) and a subsequent system (SC:H), consistent with a CWE-918 SSRF that leaks a backend API key reaching other infrastructures. The vuln.today Decision label is act_now, and the vulnerability was reported by Eclipse itself, lending vendor credibility to the affected-version range. However, key risk signals are MISSING rather than conflicting: no EPSS exploitation-probability score is provided, the CVE is not listed in CISA KEV, and the two supplied references are Eclipse GitLab vulnerability-report/CVE-assignment tracking pages, not working exploit code - so there is no public exploit identified at time of analysis. The act_now label combined with the unauthenticated-network CVSS argues for prompt patching, but the real-world blast radius is tempered by the product's narrow deployment footprint (Eclipse Mnestix is a niche Industry 4.0 Asset Administration Shell browser, not ubiquitous enterprise software). Net: a high-severity, credible, act_now-rated credential-exposure flaw whose theoretical ease of exploitation is high but whose observed exploitation and automation signals are currently unverified.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request to an exposed Eclipse Mnestix Browser instance (version 1.6.0 through pre-2.3.0) and abuses the SSRF condition to retrieve the MNESTIX_BACKEND_API_KEY configured for all Infrastructures. With that key, the attacker can then authenticate to and act against the backend services those keys protect. No authentication or user interaction is required per the CVSS vector (PR:N/UI:N), though no working public exploit code has been identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

Eclipse Mnestix Browser 1.6.0 through releases before 2.3.0 allows unauthenticated remote attackers to exfiltrate the MNESTIX_BACKEND_API_KEY for every configured Infrastructure. The issue is classified as CWE-918 (SSRF) with a CVSS 4.0 base score of 9.2 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N), and the independent CVSS 3.1 vector confirms network reachability, no privileges, no user interaction, and high confidentiality impact. No public exploit code or CISA KEV entry is identified at time of analysis, but the priority label is act_now and exploitation requires only that the affected instance be reachable and have at least one Infrastructure configured with such a key.

RemediationAI

Upgrade Eclipse Mnestix Browser to 2.3.0 or later, the first release outside the stated affected range of 1.6.0 up to but excluding 2.3.0, and confirm the fixed-version guidance in the Eclipse GitLab vulnerability report (https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/773). Because MNESTIX_BACKEND_API_KEY values are the exposed secret, rotate every backend API key configured in an affected instance after upgrading and treat prior keys as compromised until rotation completes. While an upgrade is pending, restrict network access to the Mnestix Browser instance to trusted users or networks as a compensating control, recognizing that this reduces exposure but does not remediate the SSRF path. The CVE assignment reference is https://gitlab.eclipse.org/security/cve-assignment/-/work_items/302; no CISA KEV entry or public exploit code is identified in the available data.

Affected VersionsENISA

Eclipse Mnestix 1.6.0 <2.3.0

Affected Packages

euvd eclipse_mnestix fix: 2.3.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Eclipse Mnestix Browser is the affected application identified by CPE cpe:2.3:a:eclipse_foundation:eclipse_mnestix:*:*:*:*:*:*:*:*; the description limits the affected versions to 1.6.0 up to, but not including, 2.3.0. CWE-918 is Server-Side Request Forgery, a class in which a server-side component can be induced to make a request whose destination or retrieval is influenced by an attacker; in this case the disclosed impact is exfiltration of the MNESTIX_BACKEND_API_KEY values associated with configured Infrastructures. The available sources do not describe the specific endpoint, parameter, or request path that triggers the SSRF, and the trigger is not confirmed. The CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:N/UI:N with VC:H, VI:N, VA:N, SC:H, SI:N, SA:N, and the independent assessment maps to CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N; both indicate a network-reachable, unauthenticated confidentiality breach with scope change and no integrity or availability impact.

Know when Eclipse Mnestix gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (eclipse) PRIMARY 9.2 CRITICAL
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
vuln.today AI 8.6 HIGH

Remote unauthenticated SSRF needing no interaction (AV:N/AC:L/PR:N/UI:N); leaked key reaches separate backend infrastructures so S:C, and impact is confidential disclosure only (C:H/I:N/A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (eclipse).

CVSS VectorVendor: eclipse

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Nov 03, 2026 - 11:01 EUVD
CVE Published
Nov 03, 2026 - 09:31 cve.org
CRITICAL 9.2

DescriptionCVE.org

In Eclipse Mnestix Browser versions 1.6.0 up until but excluding 2.3.0 it was possible for an unauthenticated attacker to exfiltrate the MNESTIX_BACKEND_API_KEY for all configured Infrastructures.

Executive ViewAI

Why It Matters

Eclipse Mnestix Browser versions 1.6.0 through 2.2.x contain a critical unauthenticated vulnerability (CVE-2026-89292) that allows remote attackers to steal backend API keys for all configured Infrastructure integrations, potentially leading to unauthorized access to connected systems. With a CVSS score of 9.2, this flaw poses severe confidentiality risk and requires immediate remediation-no known public exploit exists yet, but the attack surface is broad and exploitation is trivial for any exposed instance.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include network segmentation to limit reachability of the Mnestix Browser instance, strict egress filtering to block SSRF, and least-privilege key scoping for Infrastructure API keys.

Threat Intelligence Overview

EPSS Score
0.5%
Top 61% exploitable
Prevalence
Low
niche open-source Industry 4.0 Asset Administration Shell browser, limited footprint
Social Media
2
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy