<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 15:03:53 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-52832</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-52832</link>
      <description>&lt;p&gt;Nuclio is a &amp;#34;Serverless&amp;#34; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuclio is a &amp;#34;Serverless&amp;#34; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-52832</guid>
    </item>
    <item>
      <title>GHSA-wpcj-rmv4-86qg — Nuclio: Unauthenticated path traversal in spec.handler allows arbitrary file write in Dashboard container</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wpcj-rmv4-86qg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nuclio/nuclio&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;During function build, `writeFunctionSourceCodeToTempFile()` passes the module name directly to `path.Join(tempDir, moduleFileName)`. Go&amp;#39;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`).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;- **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 &amp;lt;= 1.15.27 (latest at time of research, dynamically verified)&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The vulnerability spans three functions. The path from user input to disk write is:&lt;/p&gt;
&lt;p&gt;**1. `ParseHandler` — no path validation** (`pkg/functionconfig/handler.go:25-38`):&lt;/p&gt;
&lt;p&gt;```go
// pkg/functionconfig/handler.go:25-38
func ParseHandler(handler string) (string, string, error) {
    moduleAndEntryp…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nuclio/nuclio&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;During function build, `writeFunctionSourceCodeToTempFile()` passes the module name directly to `path.Join(tempDir, moduleFileName)`. Go&amp;#39;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`).&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;- **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 &amp;lt;= 1.15.27 (latest at time of research, dynamically verified)&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The vulnerability spans three functions. The path from user input to disk write is:&lt;/p&gt;
&lt;p&gt;**1. `ParseHandler` — no path validation** (`pkg/functionconfig/handler.go:25-38`):&lt;/p&gt;
&lt;p&gt;```go
// pkg/functionconfig/handler.go:25-38
func ParseHandler(handler string) (string, string, error) {
    moduleAndEntryp…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wpcj-rmv4-86qg</guid>
    </item>
  </channel>
</rss>
