Homepage

Algorithmic Complexity Affecting argo-workflow-controller-fips-3.6 package, versions *

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.37% (31st 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-MINIMOSLATEST-ARGOWORKFLOWCONTROLLERFIPS36-21788070
  • published29 Oct 2026
  • disclosed26 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 26 Oct 2026

NewCVE-2026-116587  (opens in a new tab)
CWE-407  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest argo-workflow-controller-fips-3.6.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflow-controller-fips-3.6 package and not the argo-workflow-controller-fips-3.6 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.6, go-jose parses attacker-controlled RSA modulus and prime values from JWKs without enforcing size and consistency bounds before passing them to crypto/rsa.PrivateKey.Validate. On Go 1.24 and later, crafted large or degenerate RSA parameters can make that validation consume cubic CPU time, allowing remote denial of service in applications that parse JWKs from untrusted sources. This issue is fixed in version 4.1.6.