{"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-52833 exists.","fix":"Upgrade github.com/nuclio/nuclio to 1.16.5 or later.","what":"CVE-2026-52833 is a high-severity code injection 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-52833 and fix it if it is affected.\n\nWhat it is: CVE-2026-52833 is a high-severity code injection 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-52833 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-52833/ (Markdown: https://insights.sbomify.com/CVE-2026-52833/index.md)","id":"CVE-2026-52833","markdown":"https://insights.sbomify.com/CVE-2026-52833/index.md","name":"CVE-2026-52833","record":{"aliases":["GHSA-3v79-m2cg-89ww","GO-2026-6004"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Serverless framework","requires_auth":"high_privilege","summary":"Attackers can inject arbitrary Groovy code into build files via unsanitized repository attributes, leading to remote code execution during function builds.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Nuclio is a \"Serverless\" framework for Real-Time Events and Data Processing. Prior to version 1.16.5, 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. This issue has been patched in version 1.16.5.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Nuclio: Unsanitized runtimeAttributes.repositories injected into Groovy build.gradle leads to build-time RCE","id":"CVE-2026-52833","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"jxl-oxide: Out-of-bounds writes due to integer overflow in jxl-grid on 32-bit platforms","id":"CVE-2026-52834"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":"pkg:golang/github.com/nuclio/nuclio","source":"GO-2026-6004"},{"ecosystem":"Go","fixed":["1.16.5"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":null,"source":"GHSA-3v79-m2cg-89ww"},{"ecosystem":"Go","fixed":["1.16.5"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":"pkg:golang/github.com/nuclio/nuclio","source":"GHSA-3v79-m2cg-89ww"}],"prev":{"headline":"Nuclio: Unauthenticated path traversal in spec.handler allows arbitrary file write in Dashboard container","id":"CVE-2026-52832"},"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["nuclio"]},"summary":"Attackers can inject arbitrary Groovy code into build files via unsanitized repository attributes, leading to remote code execution during function builds.","url":"https://insights.sbomify.com/CVE-2026-52833/"}