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.

Remediation

No solution or workaround provided in the CVE record

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

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