Skip to content
Cloud

CVE-2026-79755

8.0
High
EPSS 0.40%Patch availableSep 3, 2026

Command injection in Nuclio dashboard namespace handling leading to host compromise

common questions

Is CVE-2026-79755 being exploited?

Not confirmed. CVE-2026-79755 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.40% probability of exploitation in the next 30 days.

How severe is CVE-2026-79755?

CVE-2026-79755 is rated High with a CVSS score of 8.0. 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-79755?

Yes. A fix has been recorded for CVE-2026-79755. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-79755 affect?

CVE-2026-79755 affects Nuclio <1.17.4 (local Docker/dashboard), Dashboard container with host Docker socket, Deployments using 'nop' (unauthenticated) auth. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-79755?

Upgrade Nuclio to >=1.17.4; disable 'nop' auth; remove/restrict Docker socket from containers.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Nuclio <1.17.4 (local Docker/dashboard)Dashboard container with host Docker socketDeployments using 'nop' (unauthenticated) auth
impact

Remote OS command injection via namespace interpolation; attacker can run root commands in dashboard container and compromise host via Docker socket.

action required

Immediate action required

affected versions
nuclio nuclio
  • affected< 1.17.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free