Skip to main content
VulnerabilityPublished

CVE-2026-55602: Argo workflows · http-proxy-middleware is node

Affects argo-workflowsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-55602· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.1.6-r1 when convenient.

Data as of 11 Nov 2026, 04:32 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.1.6-r1, 4.0.15-r2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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; argo-workflows to 4.0.15-r2.

Affected software

ProductAffectedFixed in
CleanStartargo-workflowspkg:apk/cleanstart/argo-workflowsOther threatsAffected
  • <4.1.6-r1
Fixed in
  • 4.1.6-r1
CleanStartargo-workflowspkg:apk/cleanstart/argo-workflowsOther threatsAffected
  • <4.0.15-r2
Fixed in
  • 4.0.15-r2

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 4.0.15-r2 or later to remediate this vulnerability. Since patchAvailable is true and fixedVersions are known, applying these official fixes is the recommended mitigation. No additional vendor advisory indicates alternative mitigations or no action required.

Description

A high-severity security vulnerability (CVE-2026-55602) affects the argo-workflows package due to an issue in the http-proxy-middleware component used in Node.js environments. The vulnerability impacts versions prior to 4.1.6-r1 and 4.0.15-r2. It allows an attacker to cause a complete compromise of integrity without affecting confidentiality or availability. The vulnerability has been fixed in versions 4.1.6-r1 and 4.0.15-r2.

References

Community reviews

Loading reviews…