Vulnerability · Published Oct 29, 2026 · Assigned by GitHub_M
CVE-2026-118777Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie
Medium 4.8
In plain English
A medium-severity prototype pollution in forge from digitalbazaar. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 20% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
Forge (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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu:22.04:LTS | node-node-forge | no fix listed | UBUNTU-CVE-2026-118777 |
| npm | node-forge | 1.4.1 | GHSA-6wvx-3r32-xmcg |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| digitalbazaar | forge | < 1.4.1 |
Weakness: CWE-1321 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L