CVE-2026-7412: Org.eclipse.basyx:basyx.sdk: Eclipse BaSyx Java Server SDK vulnerable to Server-Side Request Forgery
Affects org.eclipse.basyx:basyx.sdkSource GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 2.0.0-milestone-10 soon.
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:N/A:NExploitation 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, the Operation Delegation feature fails to validate the destination URI of delegated requests. An unauthenticated remote attacker can exploit this design flaw to force the BaSyx server to execute blind HTTP POST requests to arbitrary internal or external targets. This allows an attacker to bypass network segmentation and pivot into isolated internal IT/OT infrastructure or target Cloud Metadata services (IMDS).