Improper Verification of Cryptographic Signature Affecting argo-workflows-ui-fips-3.7 package, versions <3.7.8-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.1% (1st 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-ARGOWORKFLOWSUIFIPS37-22424360
  • published12 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-118774  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade Minimos:latest argo-workflows-ui-fips-3.7 to version 3.7.8-r0 or higher.

NVD Description

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

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer's private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.

CVSS Base Scores

version 3.1