CVE-2026-57898

Published Jul 14, 2026 CVSS 3.1 · 9 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability enables an unauthenticated attacker to perform arbitrary file writes on a server running the Eclipse BaSyx Java Server SDK with a MongoDB backend. By supplying a specially crafted fileName parameter to the AAS thumbnail upload API, the attacker can cause payload bytes to be stored at any filesystem location writable by the Java process. This flaw combines a filesystem path abuse (CWE‑22) with insecure handling of client‑controlled names (CWE‑73), potentially allowing the attacker to write executable code to a web‑accessible directory and achieve remote code execution.

Affected Systems

Affected systems include deployments of Eclipse BaSyx Java Server SDK versions 2.0.0‑milestone‑05 through 2.0.0‑milestone‑12 that use a MongoDB data store. The default InMemory backend is not affected because it sanitizes the path. The issue is fixed in milestone‑13.

Risk and Exploitability

The CVSS score is 9.0, indicating a high‑severity flaw, while the EPSS score is less than 1%, suggesting the exploitation probability is currently low. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires no authentication and leverages the thumbnail upload API, making it readily accessible to anyone who can reach the service. Attackers can remotely trigger the file write simply by sending an HTTP request with an absolute or traversal‑style filename and then initiating a thumbnail retrieval to write the file to the chosen path; if the server allows execution of files in the written directory, remote code execution becomes feasible.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Eclipse BaSyx Java Server SDK to version 2.0.0‑milestone‑13 or later, which normalizes file paths and restricts write locations.
  • If an immediate upgrade is not possible, disable or restrict the thumbnail upload endpoint and enforce authentication so that only trusted users can upload thumbnails.
  • Configure the backend filesystem permissions so that the Java process can write only to a limited directory or ensure that the repository path does not overlap with execution directories, and validate any client‑controlled fileName parameters before passing them to the filesystem.

Generated by OpenCVE AI on August 1, 2026 at 10:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Arbitrary File Write via Unauthenticated AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK
Type Values Removed Values Added
Title Arbitrary File Write via Unauthenticated AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK
Type Values Removed Values Added
First Time appeared Eclipse
Eclipse basyx - Java Server Sdk
Vendors & Products Eclipse
Eclipse basyx - Java Server Sdk
Type Values Removed Values Added
Title Unauthenticated Arbitrary File Write via AAS Thumbnail API in Eclipse BaSyx Java Server SDK
Type Values Removed Values Added
Title Unauthenticated Arbitrary File Write via AAS Thumbnail API in Eclipse BaSyx Java Server SDK
Type Values Removed Values Added
Title Unauthenticated Arbitrary File Write via AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK
Type Values Removed Values Added
Title Unauthenticated Arbitrary File Write via AAS Thumbnail Upload in Eclipse BaSyx Java Server SDK
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Weaknesses CWE-22
CWE-73
References
Metrics cvssV3_1

{'score': 9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-73

    External Control of File Name or Path

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Aug 31, 2026, 12:27 PM
Reserved
Jul 8, 2026, 2:11 PM
Status
Awaiting Analysis
Published
Jul 14, 2026, 9:16 AM
Modified
Jul 14, 2026, 4:38 PM