# Eclipse BaSyx Java Server SDK vulnerable to Path Traversal

Advisory record · `GHSA-8gpm-h2mh-36qc`

- **Identifiers:** `GHSA-8gpm-h2mh-36qc` · `CVE-2026-7411`
- **State:** Confirmed
- **Severity:** CVSS 10.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 5 May 2026
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 May 2026, 18:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 10.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.eclipse.basyx:basyx.sdk` (Maven): affected `<2.0.0-milestone-10`; fixed in `2.0.0-milestone-10`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Eclipse BaSyx Java Server SDK (basyx.sdk) versions before 2.0.0-milestone-10 are vulnerable to path traversal in the Submodel HTTP API. An unauthenticated remote attacker can supply a crafted fileName parameter during a file upload to write files to arbitrary locations on the host, which can lead to remote code execution and full system compromise. Upgrade to 2.0.0-milestone-10 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, from CNA (eclipse)

- **CISA KEV:** Not listed.
- **EPSS:** 0.037, the 89th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8gpm-h2mh-36qc)

## Sources

- [GitHub Advisory Database: GHSA-8gpm-h2mh-36qc](https://github.com/advisories/GHSA-8gpm-h2mh-36qc)
- [OSV: GHSA-8gpm-h2mh-36qc](https://osv.dev/vulnerability/GHSA-8gpm-h2mh-36qc)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-7411>
- <https://github.com/eclipse-basyx/basyx-java-sdk>
- <https://gitlab.eclipse.org/security/cve-assignment/-/issues/102>
- <https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/423>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8gpm-h2mh-36qc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8gpm-h2mh-36qc/>. Everything for agents: <https://agentprime.io/llms.txt>.