Skip to main content

Eclipse BaSyx CVE-2026-57898

| EUVDEUVD-2026-43635 CRITICAL
Path Traversal (CWE-22)
2026-07-14 eclipse GHSA-4w7g-2ph6-pm6g
9.0
CVSS 3.1 · Vendor: eclipse
View

Attack ChainAIDerived

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

  1. Access
    Reach network-exposed AAS thumbnail API
  2. Delivery
    Upload thumbnail with traversal/absolute fileName
  3. Exploit
    GridFS stores unnormalized attacker key
  4. Execution
    Trigger thumbnail retrieval to flush bytes
  5. Persist
    Write file to attacker-chosen path
  6. Impact
    Achieve code execution as Java process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

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

Exploitation Conditions

Exploitation requires the BaSyx server to be deployed with the MongoDB (GridFS) file repository backend - the default InMemory backend is not affected because it normalizes and restricts paths to its temporary directory. The attacker must reach the AAS thumbnail API over the network and perform two steps: upload thumbnail content with an absolute or traversal-style fileName, then trigger thumbnail retrieval so the bytes are flushed to the chosen filesystem path. No authentication or user interaction is needed (PR:N, UI:N), but exploitation is limited by the non-default backend requirement, the two-step upload-then-retrieve sequence (reflected as AC:H), and the file permissions of the Java process - writes only succeed where that process can write, and escalation to RCE depends on a writable, code-executing target path being available.

Impact

The CVSS 3.1 score of 9.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects a network-reachable, unauthenticated flaw with scope change and high impact across confidentiality, integrity, and availability, tempered by AC:H. The high attack complexity is consistent with the description: exploitation only works on deployments configured with the MongoDB backend and requires a two-step upload-then-retrieve sequence, so this is not a spray-and-pray bug against every install. No EPSS score, KEV listing, or POC was provided, so real-world exploitation pressure is presently unquantified - treat the score as a capability ceiling rather than evidence of active targeting. The PR:N rating is vendor-supplied and matches the 'unauthenticated' language in the description. Net assessment: a genuine high-priority issue for any organization actually running BaSyx on the MongoDB backend, but the non-default backend requirement meaningfully narrows the exposed population; low prevalence of the product overall keeps aggregate risk contained.

Exploit ScenarioDerived

An attacker who can reach a BaSyx server running the MongoDB backend uploads thumbnail content while supplying a traversal or absolute-path fileName such as one pointing at a web-exec directory or a startup/cron location. They then invoke thumbnail retrieval, causing the server to write the attacker-controlled bytes to that path, which can be leveraged for remote code execution. No public exploit code was identified at time of analysis, and the AC:H rating reflects the required MongoDB configuration plus the multi-step trigger.

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

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

Alert me

AnalysisAIv1 – Jul 14, 2026

Unauthenticated arbitrary file write in Eclipse BaSyx Java Server SDK (2.0.0-milestone-05 through 2.0.0-milestone-12) lets remote attackers plant files anywhere the Java process can write when the server is deployed with the MongoDB file backend, potentially escalating to remote code execution. The AAS thumbnail API trusts a client-supplied fileName that is later reused as a filesystem path, so a traversal or absolute-path filename lands attacker-controlled bytes outside the intended directory. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, but the vendor-fixed release (2.0.0-milestone-13) is available.

RemediationAI

Upgrade to Eclipse BaSyx Java Server SDK 2.0.0-milestone-13, which contains the vendor fix (Vendor-released patch: 2.0.0-milestone-13); this is the primary and recommended action. If you cannot upgrade immediately, the most effective compensating control is to switch the file repository from the MongoDB backend to the default InMemory backend, which normalizes and confines file paths and is not affected - the trade-off is loss of MongoDB-backed persistence for AAS files. Additional interim measures include restricting network access to the AAS thumbnail upload/retrieval endpoints to trusted clients only (via a reverse proxy or network ACL, accepting reduced accessibility for legitimate integrations) and running the BaSyx Java process under a least-privilege account so any successful write is confined to non-sensitive directories, reducing but not eliminating RCE potential. Track remediation details via https://gitlab.eclipse.org/security/cve-assignment/-/work_items/159.

Affected VersionsENISA

Eclipse BaSyx - Java Server SDK 2.0.0-milestone-05 <2.0.0-milestone-13

Affected Packages

euvd eclipse_basyx_java_server_sdk fix: 2.0.0-milestone-13

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 BaSyx is an open-source implementation of the Industrie 4.0 Asset Administration Shell (AAS), and this flaw lives in the AAS repository's thumbnail upload/retrieval feature. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / path traversal): a single client-controlled fileName parameter is overloaded as both a repository key and a local filesystem path. With the MongoDB (GridFS) file repository, the value is treated as an opaque GridFS key and is never normalized or constrained to a base directory, so during thumbnail retrieval the same string is used to write to disk at an attacker-chosen location. The CPE cpe:2.3:a:eclipse_foundation:eclipse_basyx_-_java_server_sdk confirms the affected component is the Java Server SDK. The default InMemory backend is not exploitable through this path because it normalizes and confines paths to its temporary directory.

Know when Eclipse Basyx Java Server Sdk 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.0 CRITICAL
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.9 HIGH

Network unauthenticated (AV:N/PR:N) but AC:H due to required MongoDB backend and two-step trigger; primary impact is arbitrary write (I:H) with potential RCE (A:H), limited direct read (C:L), and S:C for writing outside the intended store.

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

Primary rating from Vendor (eclipse).

CVSS VectorVendor: eclipse

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Jul 14, 2026 - 11:17 EUVD
CVE Published
Jul 14, 2026 - 07:51 cve.org
CRITICAL 9.0

DescriptionCVE.org

In Eclipse BaSyx Java Server SDK versions 2.0.0-milestone-05 to 2.0.0-milestone-12, deployments using the MongoDB backend are vulnerable to an unauthenticated arbitrary file write through the AAS thumbnail API.

The AAS thumbnail upload path accepted a client-controlled fileName request parameter and passed it through repository file handling as both a repository key and, during thumbnail retrieval, a local filesystem path. With the MongoDB file repository, the supplied filename was treated as an opaque GridFS key and was not normalized or restricted as a filesystem path. A remote attacker could upload thumbnail content using an absolute or traversal-style filename, then trigger thumbnail retrieval so that the uploaded bytes were written to the attacker-chosen path on the server filesystem.

This could allow writing files anywhere the Java process has permission to write and may lead to remote code execution. The default InMemory backend is not affected by this specific path because it normalizes and restricts file paths to its temporary directory.

The issue is fixed in Eclipse BaSyx Java Server SDK 2.0.0-milestone-13.

Executive ViewAI

Why It Matters

Eclipse BaSyx Java Server SDK versions 2.0.0-milestone-05 through milestone-12 contain a critical unauthenticated arbitrary file write vulnerability in the AAS thumbnail API that enables remote code execution on systems deployed with MongoDB file backend. Organizations running affected versions can be compromised by remote attackers without credentials; server compromise and malicious code execution pose direct business continuity and data integrity risks. Immediate upgrade to version 2.0.0-milestone-13 is required.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 64% exploitable
Prevalence
Low
niche Industrie 4.0 Asset Administration Shell SDK, industry-specific footprint
Social Media
4
Sightings
Data Quality
5 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.4%
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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