The `forge.http` client stores cookie names and paths from Set-Cookie response headers in ordinary JavaScript objects. A malicious server can exploit this by using the cookie name ` proto ` to write an attacker-controlled cookie path as a property on `Object.prototype`, or by using inherited names like `constructor` to modify the `Object`. Additionally, an empty cookie value can be used via the removal path to delete an inherited `Object.prototype` property. This affects applications using `forge.http` directly or through `forge.xhr`.