Answer in brief
CVE-2026-52831 records a Critical severity (CVSS 8.0) vulnerability in Nuclio: Unsanitized cron trigger event headers/body injected into CronJob shell command leads to persistent RCE. The current sources do not mark it as known exploited. The current feed maps nuclio/nuclio (generic), github.com/nuclio/nuclio (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps nuclio/nuclio (generic), github.com/nuclio/nuclio (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| nuclio/nucliogeneric | < 1.16.4 | Not reported |
| github.com/nuclio/nucliogo | <0.0.0-20260601075854-3356b86a8bfa | 0.0.0-20260601075854-3356b86a8bfa |
Published upstream
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 8, 2026
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, <command>). 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.
Quoted source text, attributed separately from HOL analysis.