{"answers":{"affected":"3 open source packages ship an affected version, including github.com/nuclio/nuclio.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52832 exists.","fix":"Upgrade github.com/nuclio/nuclio to 1.16.5 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-52832 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52832 exists.\n\nAffected packages and fixed versions:\n- github.com/nuclio/nuclio (Go): affected all versions; no fix listed\n- github.com/nuclio/nuclio (Go): affected all versions; fixed in 1.16.5\n- github.com/nuclio/nuclio (Go): affected all versions; fixed in 1.16.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-52832/ (Markdown: https://insights.sbomify.com/CVE-2026-52832/index.md)","id":"CVE-2026-52832","markdown":"https://insights.sbomify.com/CVE-2026-52832/index.md","name":"CVE-2026-52832","record":{"aliases":["GHSA-wpcj-rmv4-86qg","GO-2026-6012"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Nuclio serverless framework","requires_auth":"high_privilege","summary":"Unauthenticated attackers can write arbitrary files via path traversal in the Nuclio Dashboard, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":"2026-07-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-29T10:23:41Z","kind":"github_poc","ref":"https://github.com/mdvpat/CVE-2026-52832-PoC-exploit-nuclio-dashboard","stars":0,"title":"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)"}],"tier":"weaponised"},"has_fix":true,"headline":"Nuclio: Unauthenticated path traversal in spec.handler allows arbitrary file write in Dashboard container","id":"CVE-2026-52832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Nuclio: Unsanitized runtimeAttributes.repositories injected into Groovy build.gradle leads to build-time RCE","id":"CVE-2026-52833"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":"pkg:golang/github.com/nuclio/nuclio","source":"GO-2026-6012"},{"ecosystem":"Go","fixed":["1.16.5"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":null,"source":"GHSA-wpcj-rmv4-86qg"},{"ecosystem":"Go","fixed":["1.16.5"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":"pkg:golang/github.com/nuclio/nuclio","source":"GHSA-wpcj-rmv4-86qg"}],"prev":{"headline":"Nuclio: Unsanitized cron trigger event headers/body injected into CronJob shell command leads to persistent RCE","id":"CVE-2026-52831"},"products":["nuclio"],"published":"2026-09-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["nuclio"]},"summary":"Unauthenticated attackers can write arbitrary files via path traversal in the Nuclio Dashboard, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-52832/"}