Argo workflows: Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0)
Affects argo-workflowsSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.1.6-r1 soon.
Data as of 11 Nov 2026, 03:50 UTC
- Patch
- Available – fixed in 4.1.6-r1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 May 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 to argo-workflows version 4.1.6-r1 or later, where this issue is fixed. Applying this update will prevent the panic caused by NUL characters in inputs to the Dial and LookupPort functions.
Description
A security vulnerability in the argo-workflows package causes the Dial and LookupPort functions to panic on Windows when given input containing a NUL (0) character. This issue affects versions prior to 4.1.6-r1 and can lead to denial of service due to application crashes.