Skip to main content
No exploitation reportedFix available

CVE-2025-32445

No exploitation reported by the sources we read.

  • Published2025-04-15
  • Fixed in1.9.6
  • WeaknessCWE-250

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2025-04-1520:15CVE publishedNVD

Versions per branch

OSV
argoproj/argo-events
BranchAffectedFixed in
1.9< 1.9.61.9.6

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • argoproj argo-events
    Affected
    • = < 1.9.6no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-04-15

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • argo-events-fipsChainguardall versions · fixed in 1.9.6-r0
  • argo-workflowsWolfiall versions · no fixed version listed
  • argo-workflowsChainguardall versions · no fixed version listedand 1 other package
  • argo-workflows-fipsCleanStartall versions · fixed in 3.5.15-r1
  • github.com/argoproj/argo-eventsRoot:Goall versions · fixed in v1.9.1-aikido.2
  • govulncheck-vulndbopenSUSE:Tumbleweedall versions · fixed in 0.0.20250422T181640-1.1
  • rootio-github.com/argoproj/argo-eventsRoot:Goall versions · fixed in v1.9.1-root.io.1
  • rootio-github.com/argoproj/argo-eventsRoot:Goall versions · fixed in v1.9.1-root.io.2

Full record on NVD

Fix

  1. Update argoproj/argo-events to 1.9.6

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2025-04-15
  • CNACVSS 3.19.9known since 2026-10-23
  • CNAweakness (CWE)CWE-250known since 2026-10-23
  • FIRST EPSSEPSS score0.8 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2025-04-14

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Published
2025-04-15
Last Modified
2026-06-17
NVD status
Deferred
GitHub Advisory
GHSA-hmp7-x699-cvhq

Frequently asked questions

What is CVE-2025-32445?

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.

Is CVE-2025-32445 actively exploited?

Active exploitation of CVE-2025-32445 has not been confirmed. Its EPSS score was 0.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-32445?

CVE-2025-32445 has a CVSS v3 base score of 9.9 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Running argo-workflows? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record