Security Digest · Vulnerability record
CVE-2026-7411: Eclipse BaSyx Java Server SDK vulnerable to Path Traversal
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.
CVSS 10.0 Critical EPSS 1.5% · p74
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 1.5%, percentile 74: FIRST’s model estimates a 1.5% chance of exploitation activity in the next 30 days, higher than 74% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
org.eclipse.basyx:basyx.sdk(Maven) < 2.0.0-milestone-10, fixed in 2.0.0-milestone-10. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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.
Weakness type: CWE-22.
Product: org.eclipse.basyx:basyx.sdk (Maven) · Assigned by: eclipse · Published: 2026-05-05
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Maven | org.eclipse.basyx:basyx.sdk | < 2.0.0-milestone-10 | 2.0.0-milestone-10 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Eclipse Foundation | Eclipse BaSyx | < 2.0.0-milestone-10 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| eclipse | 3.1 | 10 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 1.52% probability of exploitation activity in the next 30 days; percentile 74.
Timeline
- — CVE record published by eclipse
- — GitHub-reviewed advisory GHSA-8gpm-h2mh-36qc published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-8gpm-h2mh-36qc github.com
- CVE.org record CVE-2026-7411 cve.org
- NVD entry CVE-2026-7411 nvd.nist.gov
Other references from the CVE record and advisory
- gitlab.eclipse.org gitlab.eclipse.org
- gitlab.eclipse.org gitlab.eclipse.org