CVE-2026-66297

Unescaped deployment environment variables in generated setup commands

HIGH
8
CVSS Score
Published: August 5, 2026 at 07:43 PM UTC
Updated: October 24, 2026 at 04:10 PM UTC
2 products affected across 2 vendorsLivebookLivebook

Using livebook by livebook-dev?

Get instant alerts when new vulnerabilities affect livebook - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8
Exploit prediction
EPSS 2%
SSVC
PoC

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions0.13.00.13.0-cuda120.19.00.19.0-cuda127cf4af5c10ec645f55a10f30e5661c54f6a6b319
Affected range stops below 0.18.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.18.7-cuda12, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.19.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.19.9-cuda12, so it looks safe — our inference, not a vendor statement
0.13.0 ≤ v < 0.18.70.19.0 ≤ v < 0.19.9
Affected range stops below 0.18.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.19.9, so it looks safe — our inference, not a vendor statement

References (6)

RelatedVendor Advisory
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
https://cna.erlef.org/cves/CVE-2026-66297.html
Vendor AdvisoryRelatedExploitPatch
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
https://github.com/livebook-dev/livebook/security/advisories/GHSA-qpjc-w5mm-73mj
RelatedThird Party Advisory
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
https://osv.dev/vulnerability/EEF-CVE-2026-66297

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-78

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card