CVE-2026-66297: Unescaped deployment environment variables in generated setup commands

Published Aug 5, 2026
·
Updated

Summary

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.dockerinstructions/2 and LivebookWeb.Hub.Teams.DeploymentGroupAgentComponent.flyinstructions/4 in lib/livebookweb/live/hub/teams/deploymentgroupagentcomponent.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.onlinedockerinfo/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.

Other sources

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.dockerinstructions/2 and LivebookWeb.Hub.Teams.DeploymentGroupAgentComponent.flyinstructions/4 in lib/livebookweb/live/hub/teams/deploymentgroupagentcomponent.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.onlinedockerinfo/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.

— NVD

Affected Software

5 affected componentsFixes available
livebook-dev livebook>=0.13.0<0.18.7, >=0.19.0<0.19.9
Livebook Livebook>=0.13.0<0.18.7
Livebook Livebook>=0.19.0<0.19.9
erlang/livebook>=0.13.0<0.18.7
0.18.7
erlang/livebook>=0.19.0<0.19.9
0.19.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade erlang/livebook to a version that resolves this vulnerability.

    Fixed in 0.18.7
  2. Upgrade

    Upgrade erlang/livebook to a version that resolves this vulnerability.

    Fixed in 0.19.9
  3. Upgrade

    Upgrade livebook-dev/livebook to a version that resolves this vulnerability.

    Fixed in 0.18.7
  4. Upgrade

    Upgrade livebook-dev/livebook to a version that resolves this vulnerability.

    Fixed in 0.19.9

Event History

Aug 5, 2026
CVE Published
via MITRE·07:43 PM
Data Sourced
via MITRE·07:43 PM
DescriptionWeakness
Data Sourced
via OSV·07:43 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·08:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 6, 2026
Exploit Published
via CISA·01:04 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-66297?

CVE-2026-66297 has a risk rating of 37, indicating a significant security concern.

2

How do I fix CVE-2026-66297?

To fix CVE-2026-66297, update to the latest version of livebook-dev livebook that addresses the command injection vulnerability.

3

What type of vulnerability is CVE-2026-66297?

CVE-2026-66297 is classified as an OS Command Injection vulnerability.

4

Where can CVE-2026-66297 be found in livebook-dev livebook?

CVE-2026-66297 can be found in the docker_instructions/2 function within the LivebookWeb.Hub.Teams.DeploymentGroupAgentComponent.

5

What are the potential impacts of CVE-2026-66297?

The potential impacts of CVE-2026-66297 include unauthorized command execution, which can compromise server integrity.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203