Argo workflows: Context was not properly tracked across template branches for JS template literals, leading to
Affects argo-workflowsSource GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.1.6-r1 when convenient.
Data as of 11 Nov 2026, 03:47 UTC
- Patch
- Available – fixed in 4.1.6-r1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Apr 2026
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.1.6-r1.
Affected software
| Product | 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
Upgrade argo-workflows to version 4.1.6-r1 or later, where this vulnerability has been fixed. Since a patch is available, applying this official fix is the recommended mitigation.
Description
A security vulnerability in the argo-workflows package was identified where context was not properly tracked across template branches for JavaScript template literals. This flaw could lead to incorrect escaping of content when branches were used, potentially causing security issues. The vulnerability affects versions prior to 4.1.6-r1 and has a medium severity rating with a CVSS score of 6.1. A fix is available in version 4.1.6-r1.