Quick answers
- Is CVE-2026-79755 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79755 being exploited in the wild.
- How severe is CVE-2026-79755?
- High severity, with a CVSS score of 8, published 2 September 2026.
- Which products and versions are affected?
- Nuclio prior to 1.17.4.
- Is there a fix for CVE-2026-79755?
- A patch was published on 2026-07-24: Fixed in version 1.17.4 via PR #4220 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-79755 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-79755?
- Check whether you run Nuclio at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an OS command injection (CWE-78) in the ShellClient.GetContainers method on the local Docker platform. The function namespace parameter is interpolated without validation into a docker ps --filter command executed via /bin/sh -c. Because the default authentication mode is nop (no authentication), any remote attacker can craft a malicious namespace value containing shell metacharacters (e.g., "; touch /tmp/pwned; echo ") to break out of the double-quoted filter token and execute arbitrary commands. The dashboard container runs as root and holds the Docker socket, enabling escalation to host compromise. The fix, applied in version 1.17.4, properly shell-escapes filter tokens using the Quote function to prevent injection. The vulnerability affects only the local Docker platform; Kubernetes deployments are not exposed.
Affected products
- Nuclio Nuclio prior to 1.17.4
Timeline
- 2026-09-02: disclosed: CVE-2026-79755 published
- 2026-07-24: patched: Fixed in version 1.17.4 via PR #4220