CVE-2026-7411: Eclipse BaSyx · Path Traversal
Affects Eclipse BaSyxSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical : upgrade to 2.0.0-milestone-10 as a priority.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 3.6% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- 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
Weaponized: 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 2 Nov 2026.
What to do
Upgrade Eclipse BaSyx to 2.0.0-milestone-10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse BaSyx | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict network access to the vulnerable service and monitor for suspicious file upload activity. Avoid exposing the affected Eclipse BaSyx Java Server SDK to untrusted networks.
Description
CVE-2026-7411 is a critical path traversal vulnerability in Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10. It allows an unauthenticated remote attacker to bypass storage boundaries by supplying a crafted fileName parameter during file upload, enabling arbitrary file writes on the host filesystem accessible to the Java process. This can lead to remote code execution and full system compromise.