CVE-2026-79756 in Nuclioinfo

Summary

by MITRE • 09/02/2026

Nuclio is a "Serverless" framework for Real-Time Events and Data Processing. Prior to version 1.17.4, the fix for unauthenticated OS command injection in the nuclio dashboard on the local/Docker platform is incomplete. The fix added validateFunctionName for function names and common.Quote() for the named-resource shell command path, but the list-all resource path (triggered when no specific resource name is provided) still interpolates the resourceNamespace parameter unquoted into a /bin/sh -c command string. An unauthenticated attacker can inject shell metacharacters via the X-Nuclio-Function-Namespace, X-Nuclio-Project-Namespace, or X-Nuclio-Function-Event-Namespace HTTP headers to achieve arbitrary command execution inside the dashboard container. This issue has been patched in version 1.17.4.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 09/02/2026

Nuclio is a serverless framework designed for real-time event and data processing, offering capabilities such as automatic scaling and low-latency response times. The vulnerability described pertains to the Nuclio dashboard component when deployed on local or Docker platforms. Prior to version 1.17.4, the application contained an incomplete fix for a previously identified unauthenticated operating system command injection flaw. While earlier patches attempted to mitigate this risk by implementing validation for function names and applying quoting mechanisms via common Quote functions to specific shell command paths, these measures were insufficiently comprehensive. Specifically, the logic handling list-all resources, which is triggered when no specific resource name is provided in a request, failed to properly sanitize or quote the resourceNamespace parameter before interpolating it into a /bin/sh -c command string. This oversight creates a critical security gap that allows for arbitrary code execution within the dashboard container environment.

The technical flaw stems from improper neutralization of special elements used in operating system commands, commonly classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command. In this scenario, the application constructs shell commands by directly concatenating user-supplied input without adequate escaping or quoting. An unauthenticated attacker can exploit this weakness by injecting shell metacharacters through specific HTTP headers associated with Nuclio requests. The vulnerable parameters include X-Nuclio-Function-Namespace, X-Nuclio-Project-Namespace, and X-Nuclio-Function-Event-Namespace. By manipulating these header values to contain malicious payloads such as semicolons or pipe characters followed by arbitrary commands, the attacker can bypass the intended command structure. The underlying shell interprets these injected elements as part of the execution flow, leading to the successful execution of unauthorized system commands with the privileges of the Nuclio dashboard process.

The operational impact of this vulnerability is severe due to its unauthenticated nature and potential for remote code execution. Since no authentication is required to trigger the list-all resource path or manipulate the relevant headers, any external actor can exploit this flaw without prior access credentials. Successful exploitation allows an attacker to gain arbitrary command execution capabilities inside the Nuclio dashboard container. This level of control enables a range of malicious activities, including but not limited to data exfiltration, lateral movement within the host network, installation of persistent backdoors, or complete compromise of the underlying infrastructure hosting the serverless functions. The attack aligns with ATT&CK technique T1059: Command and Scripting Interpreter, specifically leveraging OS-level command execution through web application vulnerabilities.

To mitigate this risk, organizations running Nuclio on local or Docker platforms must upgrade to version 1.17.4 or later, where the incomplete fix has been fully addressed by properly quoting all resource parameters interpolated into shell commands. In environments where immediate upgrading is not feasible, temporary mitigations should include restricting network access to the Nuclio dashboard interface so that it is only accessible from trusted internal networks. Additionally, implementing strict input validation and sanitization rules for HTTP headers at a reverse proxy or web application firewall level can help block requests containing shell metacharacters in namespace-related fields. Regular security audits and penetration testing are recommended to ensure that similar injection vectors do not exist elsewhere in the application logic, particularly in areas involving dynamic command construction.

Responsible

GitHub M

Reservation

08/25/2026

Disclosure

09/02/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!