Nuclio: Unsanitized runtimeAttributes.repositories injected into Groovy build.gradle leads to build-time RCE

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-52833: 0.55% estimated exploitation activity in the next 30 days; percentile 46.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Nuclio's Java runtime generates a build.gradle file during function builds using Go's text/template package. The template renders runtimeAttributes.repositories[] values with the {{ . }} action, which performs no escaping. An attacker can embed a closing brace (}) to break out of the repositories {} block and append arbitrary Groovy statements that execute unconditionally during the Gradle configuration phase. The Dashboard API runs with NOP authentication by default, so no credentials are required. The build container runs as root. The injected command output confirmed by dynamic testing: - CWE: CWE-94 (Improper Control of Generation of Code / Code Injection) - Affected versions: Nuclio <= 1.15.27 (latest as of 2026-05-17, dynamically verified) --- Details Root Cause pkg/processor/build/runtime/java/runtime.go — function createGradleBuildScript() Step 1. User input flows from the API into the template data map without validation types.go:50-64 — newBuildAttributes() decodes…

Published by the source

16 Jul 2026, 19:40 UTC

Last modified by the source

16 Jul 2026, 19:40 UTC

Source last checked

26 Oct 2026, 15:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3v79-m2cg-89ww

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-52833

Advisory: Nuclio: Unsanitized runtimeAttributes.repositories injected into Groovy build.gradle leads to build-time RCE
IDs: CVE-2026-52833, GHSA-3v79-m2cg-89ww
Record: https://patchnext.com/advisories/cve-2026-52833 (revision 1, source checked 26 Oct 2026, 15:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/nuclio/nuclio 1.16.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nuclio/nuclio: affected < 1.16.5; fixed in 1.16.5

## Suggested inspection (read-only)
- Go github.com/nuclio/nuclio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/nuclio/nuclio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3v79-m2cg-89ww (GitHub-reviewed advisory GHSA-3v79-m2cg-89ww lists affected ranges: Go github.com/nuclio/nuclio >=0 <1.16.5)

Commands are suggestions: review each one before running it.