Live › vulnerability › CVE-2026-109441
Go to dashboardLangAlpha places every tenant's sandbox container on Docker's shared default bridge network with inter-container communication enabled. An authenticated user who can run code in their own sandbox can connect to other tenants' containers and read their files, including vault secrets.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that run LangAlpha with multiple tenants on one host, where user-submitted code runs in per-tenant sandbox containers on Docker's default bridge network. Single-tenant deployments, or ones where sandboxes already sit on isolated networks, are less exposed. The sources do not say which default configuration is vulnerable beyond this.
No product ranges from the sources yet.
bridge network, for example with docker network inspect bridge and looking for the sandbox containers.com.docker.network.bridge.enable_icc set to true or unset).2026.09.07.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
LangAlpha through 2026.09.07 contains an improper isolation vulnerability that places all tenants' sandbox containers on Docker's shared default bridge network with inter-container communication enabled. Authenticated users with code execution in their own sandbox can connect directly to other tenants' containers, bypassing require_workspace_owner checks to read files such as vault secrets from exposed servers.
This page as .md · .json · in your agent: get_signal("CVE-2026-109441")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.