Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting kibana-8 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.42% (34th 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-KIBANA8-16800908
  • published23 May 2026
  • disclosed10 Jun 2026

Introduced: 23 May 2026

CVE-2026-46625  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest kibana-8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kibana-8 package and not the kibana-8 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.

CVSS Base Scores

version 3.1