{"answers":{"affected":"3 open source packages ship an affected version, including github.com/argoproj/argo-events.","exploited":"There is no known exploitation of CVE-2025-32445 in the wild and no public exploit code.","fix":"Upgrade github.com/argoproj/argo-events to 1.9.6 or later.","what":"CVE-2025-32445 is a critical vulnerability in argoproj argo-events, published on 15 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32445 and fix it if it is affected.\n\nWhat it is: CVE-2025-32445 is a critical vulnerability in argoproj argo-events, published on 15 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-32445 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/argoproj/argo-events (Go): affected all versions; fixed in 1.9.6\n- github.com/argoproj/argo-events (Go): affected all versions; fixed in 1.9.6\n- github.com/argoproj/argo-events (Go): affected all versions; fixed in 1.9.6\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-2025-32445/ (Markdown: https://insights.sbomify.com/CVE-2025-32445/index.md)","id":"CVE-2025-32445","markdown":"https://insights.sbomify.com/CVE-2025-32445/index.md","name":"CVE-2025-32445","record":{"aliases":["CLEANSTART-2025-WY26616","CLEANSTART-2025-XH32250","GHSA-hmp7-x699-cvhq","GO-2025-3608","ROOT-APP-GOBINARY-CVE-2025-32445"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes event framework","requires_auth":"low_privilege","summary":"Users with permission to create or modify EventSource and Sensor custom resources can gain privileged access to the host system and cluster.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"Argo Events is an event-driven workflow automation framework for Kubernetes. A user with permission to create/modify EventSource and Sensor custom resources can gain privileged access to the host system and cluster, even without having direct administrative privileges. The EventSource and Sensor CRs allow the corresponding orchestrated pod to be customized with spec.template and spec.template.container (with type k8s.io/api/core/v1.Container), thus, any specification under container such as command, args, securityContext , volumeMount can be specified, and applied to the EventSource or Sensor pod. With these, a user would be able to gain privileged access to the cluster host, if he/she specified the EventSource/Sensor CR with some particular properties under template. This vulnerability is fixed in v1.9.6.","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":"Users can gain privileged access to the host system and cluster with EventSource and Sensor CR","id":"CVE-2025-32445","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Null dereference in Intel QuickAssist Technology software","id":"CVE-2025-32446"},"packages":[{"ecosystem":"Go","fixed":["1.9.6"],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-events","purl":null,"source":"GHSA-hmp7-x699-cvhq"},{"ecosystem":"Go","fixed":["1.9.6"],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-events","purl":"pkg:golang/github.com/argoproj/argo-events","source":"GHSA-hmp7-x699-cvhq"},{"ecosystem":"Go","fixed":["1.9.6"],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-events","purl":"pkg:golang/github.com/argoproj/argo-events","source":"GO-2025-3608"}],"prev":{"headline":"vLLM Vulnerable to Remote Code Execution via Mooncake Integration","id":"CVE-2025-32444"},"products":["argo-events"],"published":"2025-04-15","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":"2025-04-15","vendors":["argoproj"]},"summary":"Users with permission to create or modify EventSource and Sensor custom resources can gain privileged access to the host system and cluster.","url":"https://insights.sbomify.com/CVE-2025-32445/"}