CVE-2026-3449 Affecting argo-workflows-4.0 package, versions <4.0.4-r6


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.17% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-ARGOWORKFLOWS40-16118492
  • published21 Apr 2026
  • disclosed3 Mar 2026

Introduced: 3 Mar 2026

CVE-2026-3449  (opens in a new tab)

How to fix?

Upgrade Chainguard argo-workflows-4.0 to version 4.0.4-r6 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflows-4.0 package and not the argo-workflows-4.0 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Versions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.

CVSS Base Scores

version 3.1