Homepage

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting argo-workflows-ui-3.6 package, versions <3.6.17-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.26% (18th 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-ARGOWORKFLOWSUI36-22107342
  • published1 Nov 2026
  • disclosed29 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 29 Oct 2026

NewCVE-2026-118777  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

Upgrade Minimos:latest argo-workflows-ui-3.6 to version 3.6.17-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-workflows-ui-3.6 package and not the argo-workflows-ui-3.6 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 forge.http client stored cookie names and paths from Set-Cookie response headers in ordinary JavaScript objects. A malicious server could use the cookie name proto so that the attacker-controlled cookie path was written as a property on Object.prototype, or use inherited names such as constructor to modify Object. An empty cookie value could use the removal path to delete an inherited Object.prototype property. Applications using forge.http directly or through forge.xhr are affected; applications that do not use forge.http are unaffected. This issue is fixed in version 1.4.1.