CVE-2026-52831
Command injection via unsanitized cron trigger fields in Nuclio (<1.16.4)
Is CVE-2026-52831 being exploited?
Not confirmed. CVE-2026-52831 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-52831?
CVE-2026-52831 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-52831?
Yes. A fix has been recorded for CVE-2026-52831. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-52831 affect?
CVE-2026-52831 affects Nuclio < 1.16.4, Kubernetes CronJob containers created by Nuclio cron triggers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-52831?
Upgrade Nuclio to >=1.16.4, sanitize trigger inputs, redeploy CronJobs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can inject shell commands via trigger event.headers/body, leading to command execution in Kubernetes CronJob containers.
Immediate action required
- affected< 1.16.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.