Execution with Unnecessary Privileges Affecting argo-events-fips package, versions <1.9.6-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-ARGOEVENTSFIPS-9712561
- published16 Apr 2025
- disclosed15 Apr 2025
Introduced: 15 Apr 2025
CVE-2025-32445 (opens in a new tab)How to fix?
Upgrade Chainguard argo-events-fips to version 1.9.6-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream argo-events-fips package and not the argo-events-fips package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.