SSRF (Server-Side Request Forgery) in org.eclipse.basyx:basyx.sdk (CVE-2026-7412)
Summary
SSRF in org.eclipse.basyx:basyx.sdk (CVE-2026-7412). Confidential information can be exposed externally. Mitigation: upgrade to 2.0.0-milestone-10 or later.
Original description
The description as published by the source.
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).
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-7412 has been found in org.eclipse.basyx:basyx.sdk.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade org.eclipse.basyx:basyx.sdk to 2.0.0-milestone-10 or later.
If unsure, ask your IT team or search "org.eclipse.basyx:basyx.sdk CVE-2026-7412" on the vendor's site.
CVE-2026-7412 (org.eclipse.basyx:basyx.sdk) — CWE-918 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.0-milestone-10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in org.eclipse.basyx:basyx.sdk.
Check the vendor advisory for the affected versions of org.eclipse.basyx:basyx.sdk.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 2.0.0-milestone-10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.eclipse.basyx:basyx.sdk を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.eclipse.basyx:basyx.sdk to 2.0.0-milestone-10ステージング環境で 2.0.0-milestone-10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-7412 eclipse
References
- advisory nvd.nist.gov
- package github.com
- web emo@eclipse.org
- web gitlab.eclipse.org
- web github.com