CVE-2026-15704 Eclipse BaSyx Go Components vulnerability
In Eclipse BaSyx Go Components versions up to and including 1.0.0, ABAC-enabled deployments are vulnerable to an authorization bypass caused by inconsistent trailing-slash handling between the ABAC middleware and the HTTP router. The shared router configuration used Chi's `middleware.StripSlashes`, so a request such as `GET /shells/` was dispatched to the registered `GET /shells` route. However, the ABAC middleware evaluated the original request path including the trailing slash. If ABAC route lookup did not find a matching slash-suffixed route, the request was passed onward and the router then stripped the slash and executed the protected handler without the intended ABAC authorization decision and without the expected ABAC query filters. An unauthenticated or unauthorized network attacker could append a trailing slash to protected API routes to reach handlers that should have been denied by ABAC policy. Depending on the exposed component, HTTP method, and deployed policy, this could allow unauthorized read, create, update, delete, or upload operations. The issue affects ABAC-enabled deployments of services that use the shared router and ABAC middleware, including AAS Repository, Submodel Repository, AAS Registry, Submodel Registry, Concept Description Repository, Discovery, AAS Environment upload, and related services. The issue is fixed in Eclipse BaSyx Go Components v1.0.1.
Browse Network Security security risksQuick answer
Eclipse Foundation Eclipse BaSyx Go Components should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 1.0.1
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-15704 affects Eclipse BaSyx Go Components and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Upgrade Eclipse BaSyx Go Components to 1.0.1 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Eclipse BaSyx Go Components.
- Compare the installed version with the recorded affected range: < 1.0.1.
- Upgrade Eclipse BaSyx Go Components to 1.0.1 or a later vendor-supported fixed release.
- Until patched, restrict the affected API or workflow to trusted administrators and enforce an additional access-control layer at the proxy or network boundary.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Eclipse BaSyx Go Components; remove access that is not required.
- Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-15704 in place.
- Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
CVE-2026-47724 nebula-mesh vulnerability
Updated July 24, 2026
mediumCVE-2026-56742 cilium vulnerability
Updated July 19, 2026
mediumFense Proxy & VPN Blocker <= 3.0.1 - Missing Authorization to Unauthenticated Plugin Option/Transient Deletion via fense_bpvt_save_settings AJAX Action
Updated July 19, 2026
Trusted references
FAQ
What is affected by CVE-2026-15704?
Eclipse Foundation Eclipse BaSyx Go Components versions listed as affected should be reviewed: < 1.0.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.