Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting kubeflow-centraldashboard package, versions <2.0.0-r8
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-WOLFILATEST-KUBEFLOWCENTRALDASHBOARD-22107188
- published1 Nov 2026
- disclosed29 Oct 2026
Introduced: 29 Oct 2026
NewCVE-2026-118777 (opens in a new tab)How to fix?
Upgrade Wolfi kubeflow-centraldashboard to version 2.0.0-r8 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kubeflow-centraldashboard package and not the kubeflow-centraldashboard package as distributed by Wolfi.
See How to fix? for Wolfi 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.