All reports
High

Argo Workflow may expose artifact repository credentials

Affected versions

Version ranges need review.

Affected versions
*
Fixed version
Not reported
Affected versions
<3.6.12 || >=3.7.0 <3.7.3
Fixed version
3.6.12 · 3.7.3
Affected versions
< 3.6.12
Fixed version
3.6.12
Affected versions
>= 3.7.0, < 3.7.3
Fixed version
3.7.3
Affected versions
*
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2025-62157

Probability of exploitation in the next 30 days: 0.47%

FIRST EPSS · 2026-11-19

Description

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.

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

Links

Credits

  • r0binak