Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting kibana-9.0 package, versions *
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 applicationsSnyk Learn
Learn about Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-MINIMOSLATEST-KIBANA90-17248797
- published9 Jun 2026
- disclosed10 Jun 2026
Introduced: 9 Jun 2026
NewCVE-2026-46625 (opens in a new tab)How to fix?
There is no fixed version for Minimos:latest kibana-9.0.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kibana-9.0 package and not the kibana-9.0 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
JavaScript Cookie is a JavaScript API for handling cookies, client-side. Prior to version 3.0.7, js-cookie's internal assign() helper copies properties with for...in + plain assignment. When the source object is produced by JSON.parse, the JSON object's "proto" member is an own enumerable property, so the for…in enumerates it and the target[key] = source[key] write triggers the Object.prototype.proto setter on the fresh target ({}). The result is a per-instance prototype hijack: Object.prototype itself is untouched, but the merged attributes object now inherits attacker-controlled keys. Because the consuming set() function then enumerates the merged object with another for...in, every key the attacker placed on the polluted prototype lands in the resulting Set-Cookie string as an attribute pair. The attacker can set domain=, secure=, samesite=, expires=, and path= on cookies whose attributes the developer thought were locked down. This issue has been patched in version 3.0.7.
References
- https://www.cve.org/CVERecord?id=CVE-2026-46625
- https://github.com/advisories/GHSA-qjx8-664m-686j
- https://osv.dev/vulnerability/MINI-4879-mp7p-3fp4
- https://osv.dev/vulnerability/CVE-2026-46625
- https://github.com/js-cookie/js-cookie/commit/eb3c40e89731e99b8970faaf35ddad249c6c0020
- https://github.com/js-cookie/js-cookie/releases/tag/v3.0.7
- https://github.com/js-cookie/js-cookie/security/advisories/GHSA-qjx8-664m-686j