CVE-2026-15704

{"id": "CVE-2026-15704", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-15704", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-07-24T12:30:09.827330Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "emo@eclipse.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "affected": [{"source": "emo@eclipse.org", "affectedData": [{"vendor": "Eclipse Foundation", "product": "Eclipse BaSyx Go Components", "versions": [{"status": "affected", "version": "0", "lessThan": "1.0.1", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-07-24T09:16:24.113", "references": [{"url": "https://github.com/eclipse-basyx/basyx-go-components/pull/442", "source": "emo@eclipse.org"}, {"url": "https://github.com/eclipse-basyx/basyx-go-components/releases/tag/v1.0.1", "source": "emo@eclipse.org"}, {"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/164", "source": "emo@eclipse.org"}, {"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/580", "source": "emo@eclipse.org"}, {"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/580", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "emo@eclipse.org", "description": [{"lang": "en", "value": "CWE-180"}, {"lang": "en", "value": "CWE-284"}, {"lang": "en", "value": "CWE-863"}]}], "descriptions": [{"lang": "en", "value": "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.\n\n\n\nThe 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.\n\n\n\nAn 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.\n\n\n\nThe 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."}, {"lang": "es", "value": "En las versiones de Eclipse BaSyx Go Components hasta la 1.0.0 inclusive, las implementaciones con ABAC habilitado son vulnerables a un bypass de autorizaci\u00f3n causado por un manejo inconsistente de barras finales entre el middleware ABAC y el router HTTP.\n\nLa configuraci\u00f3n compartida del router utilizaba \u201cmiddleware.StripSlashes\u201d de Chi, por lo que una solicitud como \u201cGET /shells/\u201d se despachaba a la ruta registrada \u201cGET /shells\u201d. Sin embargo, el middleware ABAC evaluaba la ruta de solicitud original incluyendo la barra final. Si la b\u00fasqueda de ruta de ABAC no encontraba una ruta coincidente con sufijo de barra, la solicitud se pasaba adelante y el router entonces eliminaba la barra y ejecutaba el gestor protegido sin la decisi\u00f3n de autorizaci\u00f3n ABAC prevista y sin los filtros de consulta ABAC esperados.\n\nUn atacante de red no autenticado o no autorizado podr\u00eda a\u00f1adir una barra final a rutas API protegidas para alcanzar gestores que deber\u00edan haber sido denegados por la pol\u00edtica ABAC. Dependiendo del componente expuesto, el m\u00e9todo HTTP y la pol\u00edtica desplegada, esto podr\u00eda permitir operaciones no autorizadas de lectura, creaci\u00f3n, actualizaci\u00f3n, eliminaci\u00f3n o carga.\n\nEl problema afecta a las implementaciones con ABAC habilitado de servicios que utilizan el router compartido y el middleware ABAC, incluyendo AAS Repository, Submodel Repository, AAS Registry, Submodel Registry, Concept Description Repository, Discovery, carga de entorno AAS y servicios relacionados. El problema est\u00e1 solucionado en Eclipse BaSyx Go Components v1.0.1."}], "lastModified": "2026-10-24T13:10:00.147", "sourceIdentifier": "emo@eclipse.org"}