CVE-2026-7411: Org.eclipse.basyx:basyx.sdk: Eclipse BaSyx Java Server SDK vulnerable to Path Traversal
Affects org.eclipse.basyx:basyx.sdkSource GCVE Database
Not known to be exploited · CVSS 10.0 Critical : upgrade to 2.0.0-milestone-10 as a priority.
Data as of 27 Oct 2026, 00:07 UTC
- Patch
- Available – fixed in 2.0.0-milestone-10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade org.eclipse.basyx:basyx.sdk to 2.0.0-milestone-10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.eclipse.basyx:basyx.sdk | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.