dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-57898

CRITICAL · 9.0 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Eclipse BaSyx Java Server SDK versions 2.0.0-milestone-05 through 2.0.0-milestone-12 contain an unauthenticated arbitrary file write vulnerability in the MongoDB backend's AAS thumbnail API. The fileName request parameter is passed directly to the repository without sanitization, allowing attackers to use absolute paths or path traversal sequences (e.g., ../../../etc/passwd) to write files to arbitrary locations on the server filesystem where the Java process has write permissions.

MitigationUpgrade to Eclipse BaSyx Java Server SDK version 2.0.0-milestone-13 or later which fixes the path normalization issue. Alternatively, avoid using the MongoDB backend until the upgrade is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Eclipse BaSyx Java Server SDK is deployed
    Search for basyx JAR files in the deployment directory, or check process list for Java processes running the BaSyx server. Look for 'basyx' in JAR names, classpath, or process arguments.
    Affected if Eclipse BaSyx Java Server SDK is found running in the environment
  2. Determine the installed version
    Check the version from the deployed JAR files (e.g., basyx-server-sdk-java-2.0.0-mXX.jar), pom.xml or build.gradle dependencies, or the startup logs. Compare the version against the affected range: 2.0.0-milestone-05 through 2.0.0-milestone-12.
    Affected if Version is 2.0.0-milestone-05, 2.0.0-milestone-06, 2.0.0-milestone-07, 2.0.0-milestone-08, 2.0.0-milestone-09, 2.0.0-milestone-10, 2.0.0-milestone-11, or 2.0.0-milestone-12
  3. Confirm MongoDB backend is in use
    Inspect the application configuration files (application.properties, application.yml, or custom config) for MongoDB connection settings. Look for 'mongo' or 'MongoTemplate' in configuration classes, or MongoDB connection URIs in the deployment.
    Affected if MongoDB is configured as the persistence backend for the AAS repository
  4. Verify the AAS thumbnail API is exposed
    Check the deployed web application for REST endpoints handling '/thumbnails' or similar AAS thumbnail operations. Review the OpenAPI/Swagger documentation if available, or check the registered servlets/filters for thumbnail upload endpoints.
    Affected if The thumbnail upload endpoint is accessible (typically /aasServer/shells/{aasId}/thumbnail or similar path under the AAS server context)
  5. Check Java process file system permissions
    Review the user context the Java process runs as (ps aux | grep java) and verify which directories that user has write access to. The vulnerability allows writing to any location the process can access.
    Affected if The BaSyx server runs with permissions to write to sensitive system directories (e.g., /etc, /var, root-owned paths)

The environment is affected if Eclipse BaSyx Java Server SDK versions 2.0.0-milestone-05 through 2.0.0-milestone-12 are deployed with the MongoDB backend and the AAS thumbnail API is exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Eclipse BaSyx Java Server SDK version 2.0.0-milestone-13 or later which fixes the path normalization issue. Alternatively, avoid using the MongoDB backend until the upgrade is possible.

Recommended fix High confidence

2.0.0-milestone-13

  1. Locate the Maven pom.xml or Gradle build configuration file for your Eclipse BaSyx Java Server SDK project
  2. Update the Eclipse BaSyx dependency version from 2.0.0-milestone-05 through 2.0.0-milestone-12 to version 2.0.0-milestone-13
  3. Run 'mvn clean install' or 'gradle build' to download and verify the updated dependencies
  4. If using a build dependency management tool (like Maven BOM or Gradle version catalog), ensure the BOM/version catalog is also updated to reference 2.0.0-milestone-13
  5. Test the application, specifically verifying the AAS thumbnail upload functionality works correctly with the fix
  6. If using MongoDB backend, confirm thumbnail retrieval writes to the expected normalized path rather than arbitrary filesystem locations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57898 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57898 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data