# CVE-2026-52832: Nuclio: Unauthenticated path traversal in spec.handler allows arbitrary file write in Dashboard container

> Unauthenticated attackers can write arbitrary files via path traversal in the Nuclio Dashboard, potentially leading to code execution.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-wpcj-rmv4-86qg, GO-2026-6012

## What is CVE-2026-52832?

CVE-2026-52832 is a medium-severity path traversal vulnerability in nuclio, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Nuclio is a "Serverless" framework for Real-Time Events and Data Processing. Prior to version 1.16.5, Nuclio Dashboard exposes POST /api/functions without authentication by default (NOP auth mode). The spec.handler field (e.g., mymodule:myfunction) is parsed by functionconfig.ParseHandler() which splits on : only — no path validation is applied to the module portion. This issue has been patched in version 1.16.5.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-52832?

3 open source packages ship an affected version, including github.com/nuclio/nuclio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/nuclio/nuclio` | Go | All versions | None |
| `github.com/nuclio/nuclio` | Go | All versions | 1.16.5 |
| `github.com/nuclio/nuclio` | Go | All versions | 1.16.5 |

## How do I fix CVE-2026-52832?

Upgrade github.com/nuclio/nuclio to 1.16.5 or later.

## Is CVE-2026-52832 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52832 exists.

Public exploit code:

- Nuclio Dashboard (NOP mode) accepts unauthenticated POST /api/functions. The spec.handler field isn't path-validated, so ../../../../tmp/x.txt:handler escapes the build tempdir via path.Join, letting an attacker write arbitrary content to any path as root. (CVE-2026-52832, ≤1.15.27) (github_poc): https://github.com/mdvpat/CVE-2026-52832-PoC-exploit-nuclio-dashboard

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52832 and fix it if it is affected.

What it is: CVE-2026-52832 is a medium-severity path traversal vulnerability in nuclio, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52832 exists.

Affected packages and fixed versions:
- github.com/nuclio/nuclio (Go): affected all versions; no fix listed
- github.com/nuclio/nuclio (Go): affected all versions; fixed in 1.16.5
- github.com/nuclio/nuclio (Go): affected all versions; fixed in 1.16.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52832/ (Markdown: https://insights.sbomify.com/CVE-2026-52832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52832
- OSV: https://osv.dev/vulnerability/CVE-2026-52832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52832/
Summaries are generated and may contain mistakes; the official description above is the record.