Argo workflows: Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP)
Affects argo-workflowsSource GCVE Database
Not known to be exploited · CVSS 9.4 Critical : upgrade to 4.0.15-r2 as a priority.
Data as of 11 Nov 2026, 04:05 UTC
Thin evidence
One scorer or none| CNA (harborist) | CVSS 4.0 | 9.4 |
|---|
- Patch
- Available – fixed in 4.0.15-r2, 4.1.6-r1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade argo-workflows to 4.0.15-r2; argo-workflows to 4.1.6-r1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartargo-workflowspkg:apk/cleanstart/argo-workflowsOther threats | Affected
| Fixed in
|
CleanStartargo-workflowspkg:apk/cleanstart/argo-workflowsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied by upgrading to argo-workflows versions 4.0.15-r2 or 4.1.6-r1. No additional mitigation steps are indicated by the vendor advisory.
Description
A critical security vulnerability in the argo-workflows package allows HTTP Parameter Pollution (HPP) due to the use of insufficiently random values in form-data. This flaw affects versions prior to 4.0.15-r2 and 4.1.6-r1. The vulnerability has a high CVSS 4.0 score of 9.4, indicating severe impact. Fixed versions 4.0.15-r2 and 4.1.6-r1 have been released to address this issue.