dbcve.org
NuclioApplication · Iguazio

CVE-2026-29042

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 1.15.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Nuclio Shell Runtime component has a command injection vulnerability where the X-Nuclio-Arguments HTTP header value is directly concatenated into shell commands without any sanitization, allowing arbitrary command execution. This affects all versions prior to 1.15.20.

MitigationUpgrade Nuclio to version 1.15.20 or later to patch the command injection vulnerability. As a temporary mitigation, consider restricting or filtering the X-Nuclio-Arguments header at the ingress layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NuclioApplication
Affected:< 1.15.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nuclio installation
    Run 'kubectl get pods -A | grep nuclio' or 'docker ps | grep nuclio' to find Nuclio containers, or check for nuclio services on the system
    Affected if No Nuclio installation found means not affected
  2. Determine Nuclio version
    Run 'kubectl get deployment -A -o jsonpath='{.items[*].spec.template.spec.containers[*].image}' | tr ' ' '\n' | grep nuclio' or check the nuclio version via the API at /api/version
    Affected if Version is below 1.15.20 (e.g., 1.15.19, 1.14.x, etc.)
  3. Check for Shell Runtime functions
    List deployed Nuclio functions with 'kubectl get functions -A' and identify any using the shell runtime (shell runtime is typically used by 'shell' or 'bash' type functions)
    Affected if Shell runtime functions are deployed and Nuclio version is below 1.15.20
  4. Inspect X-Nuclio-Arguments header handling
    Examine Nuclio gateway or worker configuration files for direct use of X-Nuclio-Arguments header in shell command execution (search for 'X-Nuclio-Arguments' in codebase or config maps)
    Affected if The header value is passed directly to shell commands without validation

You are affected if Iguazio Nuclio with a version below 1.15.20 is installed and the Shell Runtime component is in use, allowing the X-Nuclio-Arguments header to be injected into shell commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.15.20 or later
Fixed in 1.15.20
Vendor patch github.com →
Interim mitigation

Upgrade Nuclio to version 1.15.20 or later to patch the command injection vulnerability. As a temporary mitigation, consider restricting or filtering the X-Nuclio-Arguments header at the ingress layer.

Recommended fix High confidence

1.15.20

  1. Identify current Nuclio deployment version to confirm it is below 1.15.20
  2. Review Nuclio upgrade documentation for your deployment method (helm, docker, kubernetes, etc.)
  3. Back up existing Nuclio configurations, functions, and any custom resources
  4. Upgrade Nuclio to version 1.15.20 or later using your deployment method (e.g., helm upgrade for Kubernetes deployments)
  5. Verify the upgrade was successful by checking the Nuclio controller/dashboard version
  6. Test that functions execute correctly and the X-Nuclio-Arguments header is properly handled

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nuclio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29042 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data