Incorrect Regular Expression Affecting argo-workflows-ui-fips-3.6 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.44% (37th 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-ARGOWORKFLOWSUIFIPS36-21404896
  • published22 Oct 2026
  • disclosed19 Oct 2026

Introduced: 19 Oct 2026

NewCVE-2026-111755  (opens in a new tab)
CWE-185  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest argo-workflows-ui-fips-3.6.

NVD Description

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

follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.

CVSS Base Scores

version 3.1