Is there a patch available for EUVD-2026-53601?

Yes, a patch is available for EUVD-2026-53601. Update the affected software to the latest version immediately.

Livebook EUVD-2026-53601

Q: What is the CVSS score of EUVD-2026-53601?

EUVD-2026-53601 has a CVSS 4.0 base score of 4.9 (Medium). CVSS 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. EPSS exploitation probability: 1.3%.

| CVE-2026-66297 MEDIUM

OS Command Injection (CWE-78)

2026-08-05 6b3ad84c-e1a6-4bf7-a703-f496b71e49db

RCE Docker Kubernetes Command Injection Livebook

4.9

CVSS 4.0 · Vendor: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db

Severity by source

Vendor (6b3ad84c-e1a6-4bf7-a703-f496b71e49db) PRIMARY

4.9 MEDIUM

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

vuln.today AI

8.4 HIGH

PR:H for required env-var write privileges, UI:R for victim execution, S:C because impact lands on the victim's machine rather than the Livebook server.

3.1 AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Primary rating from Vendor (6b3ad84c-e1a6-4bf7-a703-f496b71e49db).

CVSS VectorVendor: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Scope

Lifecycle Timeline

Patch available

Aug 05, 2026 - 21:03 EUVD

Source Code Evidence Fetched

Aug 05, 2026 - 20:37 vuln.today

Analysis Generated

Aug 05, 2026 - 20:37 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Remote command injection in livebook-dev Livebook's deployment setup command generator allows an authenticated high-privilege attacker to poison Docker and Fly.io setup commands displayed in the web interface, causing arbitrary shell code to execute on the machine of any user who copies and runs the generated command. Affected versions span 0.13.0 through 0.18.6 and 0.19.0 through 0.19.8. No public exploit has been identified at time of analysis, though the CVSS 4.0 score of 4.9 reflects the high privileges required and the indirect execution path through a secondary user's action.

Technical ContextAI

Livebook is an Elixir-based interactive notebook platform with a Teams product that supports deploying app servers via Docker and Fly.io. The vulnerable code resides in LivebookWeb.Hub.Teams.DeploymentGroupAgentComponent (lib/livebook_web/live/hub/teams/deployment_group_agent_component.ex), specifically the docker_instructions/2 and fly_instructions/4 functions, which call Livebook.Hubs.Dockerfile.online_docker_info/3 to build setup commands. Environment variable key-value pairs sourced from the deployment group configuration are interpolated into double-quoted shell words without shell escaping, violating the expectation that double-quoting in POSIX shells prevents command substitution. CWE-78 (OS Command Injection) applies because user-controlled data reaches a shell command sink without sanitization. The root cause is that $(...) command substitutions and backtick expressions are evaluated by the shell even inside double-quoted strings, and an unescaped literal double quote breaks out of the quoting context entirely. The Kubernetes instruction path is NOT affected because it renders the same values into a YAML manifest with proper escaping. CPE: cpe:2.3:a:livebook-dev:livebook:*:*:*:*:*:*:*:* from 0.13.0 before 0.18.7 and from 0.19.0 before 0.19.9.

RemediationAI

Upgrade Livebook to version 0.18.7 or 0.19.9, both of which include the upstream fix. The patch, available via three commits (0c24873, b2a8416, f8fe9c6) and detailed in GHSA-qpjc-w5mm-73mj at https://github.com/livebook-dev/livebook/security/advisories/GHSA-qpjc-w5mm-73mj, introduces shell_quote wrapping for Docker and Fly.io environment variable interpolation in the new Livebook.Teams.DeploymentGroupInstructions module, and adds escape_dockerfile_value/1 to properly escape backslashes and double quotes in Dockerfile ENV lines. If immediate upgrade is not possible, the most effective compensating control is to restrict who can set deployment group environment variables to fully trusted users only, eliminating the attacker's injection point. As a secondary control, instruct all operators to review generated setup commands before executing them, particularly scrutinizing environment variable values for unexpected shell constructs such as $(...) or backticks. There are no known side effects from the patch - only the escaping behavior changes, not the functional output of correctly formed environment variable values.