OS Command Injection in github.com/nuclio/nuclio
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-52831 has been found in github.com/nuclio/nuclio.
Attackers can target a specific entry point like curl over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: upgrade github.com/nuclio/nuclio to 0.0.0-20260601075854-3356b86a8bfa or later.
If unsure, ask your IT team or search "github.com/nuclio/nuclio CVE-2026-52831" on the vendor's site.
CVE-2026-52831 (github.com/nuclio/nuclio) — CWE-78 / CVSS v3 8.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: curl / args / event.headers / event.body
Patched: 0.0.0-20260601075854-3356b86a8bfa — apply immediately
Workaround: set dashboard.: enabled
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in github.com/nuclio/nuclio. Attackers reach the vulnerable code path via curl without authentication.
Check the vendor advisory for the affected versions of github.com/nuclio/nuclio. Attack surface: curl / args / event.headers / event.body.
Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260601075854-3356b86a8bfa.
Workaround: set dashboard.: enabled
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/nuclio/nuclio' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'github.com/nuclio/nuclio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/nuclio/nuclioを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply temporary workaroundmitigate
set dashboard.: enabledパッチが適用されるまでの応急処置として、set dashboard.: enabled を実施。回避策の副作用 (機能低下) を確認した上で。
-
3
Apply patchpatch
Upgrade github.com/nuclio/nuclio to 0.0.0-20260601075854-3356b86a8bfaステージング環境で 0.0.0-20260601075854-3356b86a8bfa に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| go | github.com/nuclio/nuclio |
< 0.0.0-20260601075854-3356b86a8bfa |
0.0.0-20260601075854-3356b86a8bfa |
Original description The description as published by the source.
Nuclio is a "Serverless" framework for Real-Time Events and Data Processing. Prior to version 1.16.4, the 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, ). Two fields in the trigger specification flow into this string without adequate sanitization: event.headers keys and event.body. This issue has been patched in version 1.16.4.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com