CVE-2026-29042
Iguazio Nuclio ≤ 1.15.20
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-29042 is a high-severity Special Element Injection (CWE-75) vulnerability in Iguazio Nuclio. Its CVSS base score is 8.9 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-29042 is a command injection vulnerability (CWE-75) in the Nuclio Shell Runtime component of Nuclio, an open-source serverless framework for real-time events and data processing. Affecting versions prior to 1.15.20, the flaw arises when a function is invoked via HTTP, as the runtime reads the user-supplied value from the X-Nuclio-Arguments header and incorporates it directly into shell commands without validation or sanitization. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity.
The vulnerability can be exploited remotely by unauthenticated attackers with network access, requiring low complexity and no privileges or user interaction. By crafting a malicious X-Nuclio-Arguments header in an HTTP request to invoke a Nuclio function, an attacker can inject arbitrary shell commands, potentially achieving remote code execution. This grants high-impact access to confidentiality, integrity, and availability, allowing full system compromise on the hosting environment.
Mitigation is available via upgrading to Nuclio version 1.15.20, where the issue was patched. Relevant advisories and resources include the GitHub security advisory (GHSA-95fj-3w7g-4r27), the patching commit (5352d7e16cf92f4350a2f8d806c4b80b626b5c5a), pull request 4030, and the release notes for version 1.15.20.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-10013
Vulnerability Data
Nuclio is a "Serverless" framework for Real-Time Events and Data Processing. Prior to version 1.15.20, the Nuclio Shell Runtime component contains a command injection vulnerability in how it processes user-supplied arguments. When a function is invoked via HTTP, the runtime…
more
reads the X-Nuclio-Arguments header and directly incorporates its value into shell commands without any validation or sanitization. This issue has been patched in version 1.15.20.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops special-element injection by rejecting or sanitizing untrusted data before it reaches a different control plane.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input sanitization to block special-element injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing catches injection vulnerabilities but does not itself implement the sanitization fix.
Logging can record injection attempts for detection but does not prevent the weakness.
Secure development life cycle mandates input validation and sanitization practices that directly prevent special-element injection.
Application security requirements explicitly call for controls against injection flaws including special-element handling.
Secure architecture principles reduce injection surfaces but do not prescribe the actual sanitization logic.
Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.