CVE-2026-7411: Basyx.sdk Path Traversal Vulnerability

CRITICAL
Advisory Identifier: GHSA-8gpm-h2mh-36qc
CVSS 10.0
CWE-22
Published
Advisory Summary

CVE-2026-7411 is a CRITICAL (CVSS 10.0) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Basyx.sdk libraries in the Maven ecosystem. The issue involves eclipse basyx java server sdk vulnerable to path traversal. Remediation is available by upgrading affected packages to version 2.0.0-milestone-10.

CVE-2026-7411 at a Glance

CVE Identifier CVE-2026-7411
GHSA Identifier GHSA-8gpm-h2mh-36qc
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Basyx.sdk
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-7411

To remediate this vulnerability, upgrade all affected Basyx.sdk dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.eclipse.basyx:basyx.sdk fixed: 2.0.0-milestone-10
<dependency>
    <groupId>org.eclipse.basyx</groupId>
    <artifactId>basyx.sdk</artifactId>
    <version>2.0.0-milestone-10</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.eclipse.basyx

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-7411, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.eclipse.basyx

Analyze the terminal output to locate any version of Basyx.sdk in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.0-milestone-10), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.eclipse.basyx command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Basyx.sdk, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, inadequate path normalization in the Submodel HTTP API allows an unauthenticated remote attacker to perform a path traversal attack. By supplying a maliciously crafted fileName parameter during a file upload operation, an attacker can bypass intended storage boundaries and write arbitrary files to any location on the host filesystem accessible by the Java process. This can lead to Remote Code Execution (RCE) and complete system compromise.

CVE-2026-7411 Affected Basyx.sdk Versions

1 component(s)
Fixed Versions:
2.0.0-milestone-10
Product / Package Ecosystem Affected Versions Fixed Version
org.eclipse.basyx:basyx.sdk
Maven
< 2.0.0-milestone-10
2.0.0-milestone-10

References

Frequently Asked Questions

What is CVE-2026-7411?
CVE-2026-7411 is a security vulnerability in Basyx.sdk involving Eclipse BaSyx Java Server SDK vulnerable to Path Traversal under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Basyx.sdk versions are affected?
Affected versions include releases prior to 2.0.0-milestone-10 across affected packages: org.eclipse.basyx:basyx.sdk.
What version fixes CVE-2026-7411?
Upgrading to 2.0.0-milestone-10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is basyx.sdk affected?
Yes, org.eclipse.basyx:basyx.sdk is affected in releases prior to 2.0.0-milestone-10. Upgrade your dependency to 2.0.0-milestone-10 or later.
What is the CVSS score of CVE-2026-7411?
CVE-2026-7411 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-7411?
CVE-2026-7411 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Maven dependencies for CVE-2026-7411?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.eclipse.basyx'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8gpm-h2mh-36qc",
  "modified" : "2026-05-11T16:22:41Z",
  "published" : "2026-05-05T18:33:26Z",
  "aliases" : [ "CVE-2026-7411" ],
  "summary" : "Eclipse BaSyx Java Server SDK vulnerable to Path Traversal",
  "details" : "In Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, inadequate path normalization in the Submodel HTTP API allows an unauthenticated remote attacker to perform a path traversal attack. By supplying a maliciously crafted fileName parameter during a file upload operation, an attacker can bypass intended storage boundaries and write arbitrary files to any location on the host filesystem accessible by the Java process. This can lead to Remote Code Execution (RCE) and complete system compromise.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.eclipse.basyx:basyx.sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.0.0-milestone-10"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-7411"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eclipse-basyx/basyx-java-sdk"
  }, {
    "type" : "WEB",
    "url" : "https://gitlab.eclipse.org/security/cve-assignment/-/issues/102"
  }, {
    "type" : "WEB",
    "url" : "https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/423"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-11T16:22:41Z",
    "nvd_published_at" : "2026-05-05T16:16:18Z"
  }
}