CVE-2026-10054

{"id": "CVE-2026-10054", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-10054", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-07-06T00:00:00+00:00"}}], "cvssMetricV31": [{"type": "Secondary", "source": "emo@eclipse.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "affected": [{"source": "emo@eclipse.org", "affectedData": [{"vendor": "Eclipse Foundation", "product": "Eclipse Theia", "versions": [{"status": "affected", "version": "1.8.1", "lessThan": "1.73.0", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-07-03T11:16:26.847", "references": [{"url": "https://github.com/eclipse-theia/theia/security/advisories/GHSA-78g8-vm3p-97c6", "source": "emo@eclipse.org"}, {"url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/376", "source": "emo@eclipse.org"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "emo@eclipse.org", "description": [{"lang": "en", "value": "CWE-306"}, {"lang": "en", "value": "CWE-1385"}]}], "descriptions": [{"lang": "en", "value": "In affected versions of Eclipse Theia (1.8.1 and later), the browser backend exposes privileged terminal RPC over WebSocket (/services/shell-terminal, /services/terminals/:id) without service-level authentication.\n\n\n\n\nWebSocket origin validation in @theia/core is fail-open: connections are accepted when the Origin header is missing or when no THEIA_HOSTS allowlist is configured (the default). The Socket.IO integration additionally replaces the real Origin header with a client-supplied fix-origin header that an attacker can control or omit.\n\n\n\n\nAs a result, a foreign-origin web page visited by a user with a running Theia instance can open the /services WebSocket namespace, invoke terminal creation, attach to the resulting terminal data channel, execute arbitrary OS commands, and read their output. This affects both local developer setups (drive-by attack) and hosted or tunneled deployments without strong external authentication.\n\n\n\n\nA fix is in development that enforces same-origin validation by default, removes trust in the fix-origin header, gates HTTP and WebSocket access on a SameSite=Strict; HttpOnly connection-token cookie, and sanitizes shell terminal creation options."}, {"lang": "es", "value": "En las versiones afectadas de Eclipse Theia (1.8.1 y posteriores), el backend del navegador expone RPC de terminal privilegiado a trav\u00e9s de WebSocket (/services/shell-terminal, /services/terminals/:id) sin autenticaci\u00f3n a nivel de servicio.\n\nLa validaci\u00f3n de origen de WebSocket en @theia/core es de tipo \u2019fail-open\u2019: se aceptan conexiones cuando falta el encabezado Origin o cuando no hay una lista blanca THEIA_HOSTS configurada (el valor predeterminado). La integraci\u00f3n de Socket.IO adem\u00e1s reemplaza el encabezado Origin real con un encabezado \u2019fix-origin\u2019 proporcionado por el cliente que un atacante puede controlar u omitir.\n\nComo resultado, una p\u00e1gina web de origen externo visitada por un usuario con una instancia de Theia en ejecuci\u00f3n puede abrir el espacio de nombres WebSocket /services, invocar la creaci\u00f3n de terminales, adjuntarse al canal de datos del terminal resultante, ejecutar comandos arbitrarios del sistema operativo y leer su salida. Esto afecta tanto a las configuraciones de desarrollador locales (ataque de paso) como a las implementaciones alojadas o tunelizadas sin una autenticaci\u00f3n externa fuerte.\n\nSe est\u00e1 desarrollando una soluci\u00f3n que aplica la validaci\u00f3n de mismo origen por defecto, elimina la confianza en el encabezado \u2019fix-origin\u2019, restringe el acceso HTTP y WebSocket mediante una cookie de token de conexi\u00f3n SameSite=Strict; HttpOnly, y sanea las opciones de creaci\u00f3n de terminales de shell."}], "lastModified": "2026-10-25T21:10:00.770", "sourceIdentifier": "emo@eclipse.org"}