Argo workflows: webpack-dev-server is a development server that provides live reloading for webpack projects
Affects argo-workflowsSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.1.6-r1 when convenient.
Data as of 11 Nov 2026, 04:17 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 4.1.6-r1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 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
A patch is available and has been released in argo-workflows version 4.1.6-r1. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation actions are specified or required beyond applying the official fix.
Description
A security vulnerability exists in the argo-workflows package affecting versions prior to 4.1.6-r1. The issue relates to the webpack-dev-server component, which is a development server providing live reloading for webpack projects. The vulnerability has a CVSS 3.1 base score of 5.3, indicating a medium severity level with network attack vector, low attack complexity, no privileges required, no user interaction, and limited confidentiality impact. A fix is available in version 4.1.6-r1.