Skip to main content
CVE-2026-32283VulnerabilityPublished

Argo workflows: If one side of the TLS connection sends multiple key update messages post-handshake in a single

Affects argo-workflowsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-32283· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.1.6-r1 soon.

Data as of 11 Nov 2026, 04:33 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 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.

Affected software

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

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 is fixed. No other mitigation is indicated.

Description

A vulnerability in argo-workflows prior to version 4.1.6-r1 allows a TLS connection to deadlock if one side sends multiple key update messages post-handshake in a single record. This deadlock causes uncontrolled resource consumption, potentially leading to denial of service.

References

Community reviews

Loading reviews…