Bug 2511391 - CVE-2026-46625 grafana-pcp: JavaScript Cookie: Cookie attribute manipulation via prototype pollution [fedora-all]
Summary: CVE-2026-46625 grafana-pcp: JavaScript Cookie: Cookie attribute manipulation ...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: grafana-pcp
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: sfeifer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["4f5f478f-ce37-4659-a4c6-4...
Depends On:
Blocks: CVE-2026-46625
TreeView+ depends on / blocked
 
Reported: 2026-08-05 08:36 UTC by Srikanth Balasubramanian
Modified: 2026-08-05 08:36 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Srikanth Balasubramanian 2026-08-05 08:36:04 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.


Note You need to log in before you can comment on or make changes to this bug.