CVE-2026-89292
Received Received - Intake

Authentication Bypass in Eclipse Mnestix Browser

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: Eclipse Foundation

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-03
Last Modified
2026-11-03
Generated
2026-11-03
AI Q&A
2026-11-03
EPSS Evaluated
N/A
NVD
CVE-2026-89292
EUVD
EUVD-2026-115727

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse Mnestix 1.6.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-522 The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability allows an unauthenticated attacker to steal the MNESTIX_BACKEND_API_KEY from Eclipse Mnestix Browser versions 1.6.0 to 2.2.9. The flaw enables Server-Side Request Forgery (SSRF) attacks where the attacker tricks the server into making unauthorized requests. The server then attaches the private API key to these requests and returns the response, allowing the attacker to exfiltrate the key.

Detection Guidance

To detect this vulnerability, inspect Eclipse Mnestix Browser versions between 1.6.0 and 2.2.0. Check for unusual outbound HTTP requests containing API keys or responses from internal services. Monitor logs for SSRF indicators like requests to internal IPs or cloud metadata endpoints.

Impact Analysis

If exploited, this vulnerability could allow attackers to gain access to backend systems using the exposed API key. This may lead to unauthorized data access, manipulation, or service disruption. The impact depends on the privileges of the leaked key and the sensitivity of the data it protects.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR, HIPAA, or other regulations by exposing sensitive data or credentials. Unauthorized access to personal or health data may result in legal penalties, reputational damage, and loss of trust. Organizations must address this flaw to maintain regulatory compliance.

Mitigation Strategies

Upgrade Eclipse Mnestix Browser to version 2.3.0 or later immediately. If upgrading is not possible, disable affected server actions like fetchFileServerSide and transferAasWithSubmodels. Restrict outbound network access to prevent SSRF attacks and rotate the MNESTIX_BACKEND_API_KEY.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-89292. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...