<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T17:10:40.720186+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-52832</id>
    <title>fkie_cve-2026-52832</title>
    <updated>2026-09-29T17:10:41.153453+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-52832"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-wpcj-rmv4-86qg</id>
    <title>GHSA-wpcj-rmv4-86qg — Nuclio: Unauthenticated path traversal in spec.handler allows arbitrary file write in Dashboard container</title>
    <updated>2026-09-29T17:10:41.153602+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/nuclio/nuclio</p>
<p>## Summary</p>
<p>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.</p>
<p>During function build, `writeFunctionSourceCodeToTempFile()` passes the module name directly to `path.Join(tempDir, moduleFileName)`. Go's `path.Join` internally calls `path.Clean`, which resolves `../` sequences and allows the resolved path to escape `tempDir`. The function then calls `os.WriteFile` at the attacker-controlled path with attacker-controlled content (base64-decoded `spec.build.functionSourceCode`).</p>
<p>The write executes in the Dashboard container process running as `uid=0 (root)`, allowing writes to any filesystem location the process can access: `/tmp`, `/etc`, `/usr/local/bin`, `/etc/cron.d`, and more.</p>
<p>- **CVSS 3.1**: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N` — **7.5 (High)**
- **CWE**: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)
- **Affected versions**: Nuclio &lt;= 1.15.27 (latest at time of research, dynamically verified)</p>
<p>---</p>
<p>## Details</p>
<p>### Root Cause</p>
<p>The vulnerability spans three functions. The path from user input to disk write is:</p>
<p>**1. `ParseHandler` — no path validation** (`pkg/functionconfig/handler.go:25-38`):</p>
<p>```go
// pkg/functionconfig/handler.go:25-38
func ParseHandler(handler string) (string, string, error) {
    moduleAndEntryp…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-wpcj-rmv4-86qg"/>
  </entry>
</feed>
