CVE-2026-42295: Github.com/argoproj/argo workflows/v4 Argo Vulnerable To Exposure Of Vulnerability

HIGH
Advisory Identifier: GHSA-7vf8-2cr6-54mf
CWE-522
Published
Advisory Summary

CVE-2026-42295 is a HIGH argo vulnerable to exposure of vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Github.com/argoproj/argo workflows/v4 libraries in the Go ecosystem. The issue involves argo vulnerable to exposure of artifact repository credentials. Remediation is available by upgrading affected packages to version 4.0.5.

CVE-2026-42295 at a Glance

CVE Identifier CVE-2026-42295
GHSA Identifier GHSA-7vf8-2cr6-54mf
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product Github.com/argoproj/argo workflows/v4
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-42295

To remediate this vulnerability, upgrade all affected Github.com/argoproj/argo workflows/v4 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-workflows/v4 fixed: 4.0.5
Upgrade github.com/argoproj/argo-workflows/v4 to 4.0.5
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-workflows/v4

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-42295, inspect your project dependencies for Github.com/argoproj/argo workflows/v4:

inspect dependencies for github.com/argoproj/argo-workflows/v4

Analyze the terminal output to locate any version of Github.com/argoproj/argo workflows/v4 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.5), 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-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Github.com/argoproj/argo workflows/v4, 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 The workflow executor logs all artifact repository credentials (S3 access keys, secret keys, GCS service account keys, Azure account keys, Git passwords, etc.) in plaintext on artifact operation. Any user with read access to workflow pod logs can extract these credentials. **Note:** This is an incomplete fix of [CVE-2025-62157](https://github.com/argoproj/argo-workflows/security/advisories/GHSA-c2hv-4pfj-mm2r) ### Details The logging driver passes the entire ArtifactDriver struct to the structured logger, for example: https://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24 Exposed credential fields: - S3 (workflow/artifacts/s3/s3.go): AccessKey, SecretKey, SessionToken, ServerSideCustomerKey - OSS (workflow/artifacts/oss/oss.go): AccessKey, SecretKey, SecurityToken - GCS (workflow/artifacts/gcs/gcs.go): ServiceAccountKey ### PoC 1. Create template ```yml apiVersion: argoproj.io/v1alpha1 kind: Workflow metadata: name: cred-leak-test namespace: argo spec: entrypoint: main templates: - name: main container: image: alpine:3.13 command: [sh, -c] args: ["echo 'hello' > /tmp/output.txt"] outputs: artifacts: - name: output path: /tmp/output.txt s3: endpoint: minio:9000 insecure: true bucket: my-bucket key: test-output.txt accessKeySecret: name: my-minio-cred key: accesskey secretKeySecret: name: my-minio-cred key: secretkey ``` 2. Then check the logs `kubectl -n argo logs "cred-leak-test" -c wait` <img width="1248" height="322" alt="image" src="https://github.com/user-attachments/assets/a5cf6d66-7d67-408d-8583-27d11ecf1507" /> ### Impact Any user with Kubernetes RBAC permissions to read pod logs in the workflow namespace can extract artifact repository credentials.

CVE-2026-42295 Affected Github.com/argoproj/argo workflows/v4 Versions

1 component(s)
Fixed Versions:
4.0.5
Product / Package Ecosystem Affected Versions Fixed Version
github.com/argoproj/argo-workflows/v4
Go
≥ 4.0.0
< 4.0.5
4.0.5

References

Frequently Asked Questions

What is CVE-2026-42295?
CVE-2026-42295 is a security vulnerability in Github.com/argoproj/argo workflows/v4 involving Argo vulnerable to exposure of artifact repository credentials under CWE-522: Insufficiently Protected Credentials.
Which Github.com/argoproj/argo workflows/v4 versions are affected?
Affected versions include releases prior to 4.0.5 across affected packages: github.com/argoproj/argo-workflows/v4.
What version fixes CVE-2026-42295?
Upgrading to 4.0.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/argoproj/argo-workflows/v4 affected?
Yes, github.com/argoproj/argo-workflows/v4 is affected in releases prior to 4.0.5. Upgrade your dependency to 4.0.5 or later.
What CWE is associated with CVE-2026-42295?
CVE-2026-42295 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check Go dependencies for CVE-2026-42295?
Run the dependency tree command: 'inspect dependencies for github.com/argoproj/argo-workflows/v4'. 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-7vf8-2cr6-54mf",
  "modified" : "2026-07-21T13:51:11Z",
  "published" : "2026-05-04T20:12:01Z",
  "aliases" : [ "CVE-2026-42295" ],
  "summary" : "Argo vulnerable to exposure of artifact repository credentials",
  "details" : "### Summary\nThe workflow executor logs all artifact repository credentials (S3 access keys, secret keys, GCS service account keys, Azure account keys, Git passwords, etc.) in plaintext on artifact operation. Any user with read access to workflow pod logs can extract these credentials.\n\n**Note:** This is an incomplete fix of [CVE-2025-62157](https://github.com/argoproj/argo-workflows/security/advisories/GHSA-c2hv-4pfj-mm2r)\n### Details\nThe logging driver passes the entire ArtifactDriver struct to the structured logger, for example:\nhttps://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24\n\nExposed credential fields:\n- S3 (workflow/artifacts/s3/s3.go): AccessKey, SecretKey, SessionToken, ServerSideCustomerKey\n- OSS (workflow/artifacts/oss/oss.go): AccessKey, SecretKey, SecurityToken\n- GCS (workflow/artifacts/gcs/gcs.go): ServiceAccountKey\n\n### PoC\n1. Create template\n```yml\napiVersion: argoproj.io/v1alpha1\nkind: Workflow\nmetadata:\n  name: cred-leak-test\n  namespace: argo\nspec:\n  entrypoint: main\n  templates:\n  - name: main\n    container:\n      image: alpine:3.13\n      command: [sh, -c]\n      args: [\"echo 'hello' > /tmp/output.txt\"]\n    outputs:\n      artifacts:\n      - name: output\n        path: /tmp/output.txt\n        s3:\n          endpoint: minio:9000\n          insecure: true\n          bucket: my-bucket\n          key: test-output.txt\n          accessKeySecret:\n            name: my-minio-cred\n            key: accesskey\n          secretKeySecret:\n            name: my-minio-cred\n            key: secretkey\n```\n\n2. Then check the logs\n`kubectl -n argo logs \"cred-leak-test\" -c wait`\n<img width=\"1248\" height=\"322\" alt=\"image\" src=\"https://github.com/user-attachments/assets/a5cf6d66-7d67-408d-8583-27d11ecf1507\" />\n\n\n### Impact\nAny user with Kubernetes RBAC permissions to read pod logs in the workflow namespace can extract artifact repository credentials.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/argoproj/argo-workflows/v4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.0.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-workflows/security/advisories/GHSA-7vf8-2cr6-54mf"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-workflows/security/advisories/GHSA-c2hv-4pfj-mm2r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42295"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-workflows/commit/bdd40908580f727c590c8743836e338b04fe4a87"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/argoproj/argo-workflows"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-workflows/blob/59f1089b9875723ddffd524513e6bd5cb37e5e31/workflow/artifacts/logging/driver.go#L24"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-522" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-04T20:12:01Z",
    "nvd_published_at" : "2026-05-09T04:16:25Z"
  }
}