{"answers":{"affected":"3 open source packages ship an affected version, including github.com/nuclio/nuclio.","exploited":"There is no known exploitation of CVE-2026-52831 in the wild and no public exploit code.","fix":"Upgrade github.com/nuclio/nuclio to 0.0.0-20260601075854-3356b86a8bfa or later.","what":"CVE-2026-52831 is a high-severity command 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-52831 and fix it if it is affected.\n\nWhat it is: CVE-2026-52831 is a high-severity command injection vulnerability in nuclio, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-52831 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/nuclio/nuclio (Go): affected all versions; fixed in 0.0.0-20260601075854-3356b86a8bfa\n- github.com/nuclio/nuclio (Go): affected all versions; fixed in 0.0.0-20260601075854-3356b86a8bfa\n- github.com/nuclio/nuclio (Go): affected all versions; fixed in 0.0.0-20260601075854-3356b86a8bfa\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-52831/ (Markdown: https://insights.sbomify.com/CVE-2026-52831/index.md)","id":"CVE-2026-52831","markdown":"https://insights.sbomify.com/CVE-2026-52831/index.md","name":"CVE-2026-52831","record":{"aliases":["GHSA-v5px-423j-pf7p","GO-2026-5946"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Nuclio serverless framework","requires_auth":"high_privilege","summary":"Attackers can inject shell commands via cron trigger headers or body, leading to persistent remote code execution in Nuclio deployments.","user_interaction":"not_required","vuln_class":"command_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-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Nuclio is a \"Serverless\" framework for Real-Time Events and Data Processing. Prior to version 1.16.4, the Nuclio controller builds a curl invocation string for each cron trigger and stores it as the args of a Kubernetes CronJob container (/bin/sh, -c, \u003ccommand\u003e). Two fields in the trigger specification flow into this string without adequate sanitization: event.headers keys and event.body. This issue has been patched in version 1.16.4.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nuclio: Unsanitized cron trigger event headers/body injected into CronJob shell command leads to persistent RCE","id":"CVE-2026-52831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Nuclio: Unauthenticated path traversal in spec.handler allows arbitrary file write in Dashboard container","id":"CVE-2026-52832"},"packages":[{"ecosystem":"Go","fixed":["0.0.0-20260601075854-3356b86a8bfa"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":null,"source":"GHSA-v5px-423j-pf7p"},{"ecosystem":"Go","fixed":["0.0.0-20260601075854-3356b86a8bfa"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":"pkg:golang/github.com/nuclio/nuclio","source":"GHSA-v5px-423j-pf7p"},{"ecosystem":"Go","fixed":["0.0.0-20260601075854-3356b86a8bfa"],"introduced":["0"],"last_affected":[],"package":"github.com/nuclio/nuclio","purl":"pkg:golang/github.com/nuclio/nuclio","source":"GO-2026-5946"}],"prev":{"headline":"fast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protection","id":"CVE-2026-52830"},"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-03","vendors":["nuclio"]},"summary":"Attackers can inject shell commands via cron trigger headers or body, leading to persistent remote code execution in Nuclio deployments.","url":"https://insights.sbomify.com/CVE-2026-52831/"}