Argo workflows: Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript
Affects argo-workflowsSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.0.15-r2 soon.
Data as of 11 Nov 2026, 04:03 UTC
- Patch
- Available – fixed in 4.0.15-r2
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 27 Mar 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.0.15-r2.
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.0.15-r2 or later to apply the official fix. Since a patch is available, applying this update is the recommended remediation. No additional vendor advisory indicates alternative mitigations or no action required.
Description
A high-severity security vulnerability exists in the argo-workflows package due to its use of Forge (node-forge), a native JavaScript implementation of Transport Layer Security. Versions prior to 4.0.15-r2 are affected. The vulnerability does not impact confidentiality or integrity but results in high impact on availability. A fix is available in version 4.0.15-r2.