Summary
CVE-2026-79756 is an unauthenticated OS command injection vulnerability in the Nuclio dashboard’s "list-all" resource endpoint, rated HIGH severity (CVSS 8.7). It exists because an earlier fix for a related command injection issue quoted the named-resource shell command path but left the wildcard (list-all) path unquoted, allowing attackers to inject shell metacharacters via HTTP headers and execute arbitrary commands inside the dashboard container.
Technical details
- Root cause: the list-all resource code path interpolates the
resourceNamespaceparameter unquoted into a/bin/sh -ccommand string, unlike the named-resource path which applies proper shell quoting. - Trigger: sending crafted values containing shell metacharacters in the
X-Nuclio-Function-Namespace,X-Nuclio-Project-Namespace, orX-Nuclio-Function-Event-NamespaceHTTP headers when no specific resource name is supplied in the request. - Attack vector: Network, unauthenticated, no user interaction required.
- Impact: arbitrary command execution inside the Nuclio dashboard container; on local/Docker deployments this can extend to broader host/Docker compromise via the container’s access. Kubernetes-based deployments are not affected by this specific path.
Affected software
- Nuclio dashboard, versions ≤ 1.17.3 (local/Docker platform)
- Fixed in version 1.17.4
Severity
CVSS v3.1-equivalent base score: 8.7 (HIGH)
CVSS v4.0 vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: upgrade Nuclio to version 1.17.4 or later, where the list-all resource path applies proper shell-argument quoting.
- If immediate patching is not possible: restrict network access to the Nuclio dashboard (e.g., place it behind a firewall/VPN, disable direct internet exposure), and avoid running the dashboard on local/Docker platforms where the vulnerable code path is exploitable.
- Review dashboard container logs for unexpected shell commands or unusual namespace header values as an indicator of attempted exploitation.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
data-ng-app="nuclio.app" Serverresponse header:nuclio

