{"answers":{"affected":"2 open source packages ship an affected version, including org.eclipse.basyx:basyx.sdk.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7412 exists.","fix":"Upgrade org.eclipse.basyx:basyx.sdk to 2.0.0-milestone-10 or later.","what":"CVE-2026-7412 is a high-severity server-side request forgery vulnerability in Eclipse BaSyx, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7412 and fix it if it is affected.\n\nWhat it is: CVE-2026-7412 is a high-severity server-side request forgery vulnerability in Eclipse BaSyx, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7412 exists.\n\nAffected packages and fixed versions:\n- org.eclipse.basyx:basyx.sdk (Maven): affected all versions; fixed in 2.0.0-milestone-10\n- org.eclipse.basyx:basyx.sdk (Maven): affected all versions; fixed in 2.0.0-milestone-10\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7412/ (Markdown: https://insights.sbomify.com/CVE-2026-7412/index.md)","id":"CVE-2026-7412","markdown":"https://insights.sbomify.com/CVE-2026-7412/index.md","name":"CVE-2026-7412","record":{"aliases":["GHSA-gx3v-wxfj-8h24","UBUNTU-CVE-2026-7412"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse BaSyx Java SDK","requires_auth":"none","summary":"Unauthenticated attackers can force the BaSyx server to send blind HTTP POST requests to arbitrary internal or external targets, bypassing network segmentation.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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).","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Eclipse BaSyx Java Server SDK vulnerable to Server-Side Request Forgery","id":"CVE-2026-7412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Persistent undocumented backdoor access in Yarbo robot","id":"CVE-2026-7413"},"packages":[{"ecosystem":"Maven","fixed":["2.0.0-milestone-10"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.basyx:basyx.sdk","purl":null,"source":"GHSA-gx3v-wxfj-8h24"},{"ecosystem":"Maven","fixed":["2.0.0-milestone-10"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.basyx:basyx.sdk","purl":"pkg:maven/org.eclipse.basyx/basyx.sdk","source":"GHSA-gx3v-wxfj-8h24"}],"prev":{"headline":"Eclipse BaSyx Java Server SDK vulnerable to Path Traversal","id":"CVE-2026-7411"},"products":["Eclipse BaSyx"],"published":"2026-05-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-06","vendors":["Eclipse Foundation"]},"summary":"Unauthenticated attackers can force the BaSyx server to send blind HTTP POST requests to arbitrary internal or external targets, bypassing network segmentation.","url":"https://insights.sbomify.com/CVE-2026-7412/"}