Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie
Historical advisory recorded 29 Oct 2026 19:28:49 UTC. Read the latest advisory.
cve-program · CVE-2026-118777
PublishedForge (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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-118777 · CVE overview and exploitation status
cve-program · CVE-2026-118777
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.