One Forgotten Header Undid Nuclio’s Security Patch
Nuclio patched a command-injection flaw, but one forgotten path remained. A crafted namespace header can still reach a shell command and, on common local Docker deployments, the result may be root access to the underlying host.
The vulnerability, CVE-2026-79756, is an incomplete fix. It affects Nuclio versions through 1.17.3 and is fixed in 1.17.4. The Kubernetes platform is not affected by this specific path.
The dangerous input is an HTTP header
Nuclio’s local dashboard accepts namespace-related values from request headers. Researchers found that those values could still be incorporated into commands executed through /bin/sh -c. Shell metacharacters in the crafted value can therefore escape the intended argument and run attacker-controlled commands.
This is especially serious because the local Docker dashboard does not enable authentication by default. If administrators expose it beyond a trusted machine or network segment, an unauthenticated attacker may be able to reach the vulnerable request path directly.
The Docker socket turns a container bug into a host problem
Nuclio needs powerful access to create and manage functions. In Docker deployments, that commonly means access to the Docker socket. Control of that socket is effectively control of the host because an attacker can start privileged containers, mount the host filesystem and execute commands with root-level impact.
The vulnerability therefore crosses several boundaries in one chain: an unauthenticated web request influences a shell command, the shell controls the Nuclio environment, and the environment can control Docker.
Why the earlier patch did not hold
Incomplete fixes happen when developers block the payload they saw without identifying every route by which untrusted data reaches the same dangerous operation. Nuclio had already addressed related command-injection behaviour, but the namespace header remained a usable source.
The public advisory includes source-level reproduction guidance. It does not present a polished, end-to-end exploit for every deployment, and there is no confirmed malicious exploitation at publication. Even so, the primitive is clear and the default local deployment model makes exposed dashboards a priority.
What operators should do
Upgrade to Nuclio 1.17.4 or later. Do not expose the local dashboard to untrusted networks, and place authentication and network controls in front of administrative interfaces even when a project labels them as local development tools.
Teams should also inventory services with access to /var/run/docker.sock. A dashboard can look like an application-management surface while holding privileges equivalent to root. Access to the socket should be treated as a critical trust decision, logged and isolated accordingly.
After patching, review dashboard access logs for unusual namespace headers, encoded shell characters and unexpected function deployments. Inspect Docker activity and newly created containers if exposure existed.
CVE-2026-79756 is a useful warning beyond Nuclio: a fix is only as complete as the data-flow review behind it. One missed header can reopen the entire chain.
