Advisory

GHSA-c2hv-4pfj-mm2r

Also known as: BIT-argo-workflows-2025-62157, CVE-2025-62157, GO-2025-4024

Summary

Argo Workflow may expose artifact repository credentials

Details

Summary
An attacker who has permissions to read logs from pods in a namespace with Argo Workflow can read workflow-controller logs and get credentials to the artifact repository.

Details
An attacker, by reading the logs of the workflow controller pod, can access the artifact repository, and steal, delete or modify the data that resides there. The workflow-controller logs show the credentials in plaintext.

<img width="1366" alt="screen" src="https://github.com/user-attachments/assets/5642b2be-edcf-4050-bf47-747d05352698" />

Impact
An attacker with access to pod logs in the argo namespace can extract plaintext credentials from the workflow-controller logs and gain access to the artifact repository. This can lead to:

  • Data exfiltration – theft of sensitive or proprietary artifacts
  • Data tampering – modification of workflows or artifacts
  • Data destruction – deletion of stored artifacts, leading to potential loss of critical data or pipeline failure

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-10-14 18:43 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 3.7.0, fixed 3.7.3 (semver)

Fixed versions

3.7.3

Fix

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 0, fixed 3.6.12 (semver)

Fixed versions

3.6.12

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences