CVE-2026-7411
A public proof of concept exists; no exploitation attested.
- Published2026-05-05
- Fixed in2.0.0-milestone-10
- WeaknessCWE-22
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-05-0516:16CVE publishedNVD
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.0 | < 2.0.0-milestone-10 | 2.0.0-milestone-10 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As eclipse, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Eclipse Foundation Eclipse BaSyxother versions: not affectedAffected
- < 2.0.0-milestone-10fixed in 2.0.0-milestone-10custom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-05-05
Fix
- Update basyx.sdk to 2.0.0-milestone-10
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2026-05-05
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-27
- CISA-ADPSSVC decisionpoc2026-05-05
- CNACVSS 3.110known since 2026-10-27
- CNAweakness (CWE)CWE-22known since 2026-10-27
- FIRST EPSSEPSS score3.7 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryCRITICAL2026-05-11
Identifiers
- EUVD-2026-27384same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-8gpm-h2mh-36qcsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Published
- 2026-05-05
- Last Modified
- 2026-10-26
- NVD status
- Awaiting Analysis
- GitHub Advisory
- GHSA-8gpm-h2mh-36qc
Frequently asked questions
What is CVE-2026-7411?
Is CVE-2026-7411 actively exploited?
What is the CVSS score for CVE-2026-7411?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-8gpm-h2mh-36qc
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0