CVE-2026-66297
PoC nicheOS Command Injection in Livebook Docker and Fly.io deployment command generation
Livebook versions 0.13.0 through 0.18.6 and 0.19.0 through 0.19.8 contain an OS command injection flaw (CWE-78) in how the web UI generates deployment setup commands: environment variable values from a deployment group are interpolated into Docker and Fly.io setup commands without shell escaping, so shell command substitutions like $(...) or backticks inside those values are evaluated, and an embedded double quote allows arbitrary additional commands. An attacker needs privileges sufficient to set deployment group environment variables (high-privilege per the CVSS score), and exploitation requires user interaction: the injected commands execute on the machine of whoever copies the generated command from the Livebook interface and runs it without review, under that user's own account. The vulnerable system itself is not compromised; the impact is high-integrity/scope code execution on the downstream machine where the command is pasted, which is reflected in the medium CVSS 4.0 score of 5.0. Kubernetes deployment instructions are not affected because they render the same values into an escaped YAML manifest rather than a shell command. No in-the-wild exploitation is known; a public security advisory (GHSA-qpjc-w5mm-73mj) exists and EPSS estimates a 1.9% chance of exploitation in the next 30 days (78th percentile), and the flaw is not in CISA KEV.
What to do: Upgrade Livebook to 0.18.7 if running a 0.18.x release, or to 0.19.9 if running a 0.19.x release; deployments on 0.13.0-0.17.x must also move to a fixed version (0.18.7 or later). Until patched, restrict who can set deployment group environment variables, audit existing values for shell metacharacters (double quotes, $(...), backticks), and manually review generated Docker/Fly.io setup commands before running them; note that the Kubernetes instructions are not affected.
| livebook-dev livebook | >= 0.13.0, < 0.18.7; >= 0.19.0, < 0.19.9 (fixed in 0.18.7 and 0.19.9) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Improper Neutralization of Special Elements used in an OS Command (OS Command Injection) vulnerability in livebook-dev livebook allows command injection into generated deployment setup commands. LivebookWeb.Hub.Teams.DeploymentGroupAgentComponent.docker_instructions/2 and LivebookWeb.Hub.Teams.DeploymentGroupAgentComponent.fly_instructions/4 in lib/livebook_web/live/hub/teams/deployment_group_agent_component.ex interpolate deployment group environment variable values into the generated Docker and Fly.io setup commands without shell escaping. The values originate from the deployment group configuration and reach the sinks through Livebook.Hubs.Dockerfile.online_docker_info/3. Both sinks place the value inside a double-quoted shell word, so a value containing a command substitution such as $(...) or backticks is evaluated by the shell without any need to break out of the quoting, and a literal double quote terminates the quoted word and allows arbitrary further tokens. The generated command is displayed in the Livebook web interface with a copy button, so a user who copies it and runs it without reviewing it first executes the injected commands on their own machine, under their own account. An attacker requires privileges sufficient to set deployment group environment variables, while the resulting code execution occurs on the machine of whoever runs the generated command. The Kubernetes instructions are not affected, because they render the same values into a YAML manifest with escaping rather than into a shell command. This issue affects livebook: from 0.13.0 before 0.18.7 and from 0.19.0 before 0.19.9.
- Vendors
- livebook
- Products
- livebook
- Weakness
- CWE-78
- Vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
In the news0 stories
No ingested article mentions this CVE yet.