CVE-2026-118777: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie
Affects node-forgeSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 1.4.1 when convenient.
Data as of 31 Oct 2026, 01:55 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.8 |
|---|
- Patch
- Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade node-forge to 1.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnode-forge | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in node-forge version 1.4.1. Users should upgrade to this version or later. Alternatively, avoid using forge.http or forge.xhr with untrusted servers, or filter out Set-Cookie headers with names such as '__proto__', 'constructor', or other Object.prototype property names before they reach the client.
Description
A prototype pollution vulnerability exists in the forge.http client of node-forge before version 1.4.1. The client improperly stores cookies from Set-Cookie headers in a plain object keyed by cookie name and path, allowing a malicious server to use cookie names like '__proto__' or 'constructor' to modify Object.prototype or Object. This can lead to adding or deleting properties on Object.prototype, potentially altering application logic or breaking functionality. The issue is fixed in node-forge 1.4.1 by ignoring such dangerous cookie names and paths.
References
- github.com/digitalbazaar/forge/security/advisories/GHSA-6wvx-3r32-xmcg (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-118777 (opens in a new tab)
- github.com/digitalbazaar/forge/commit/797c3f816a22748a96fceebb34eb3a6716853991 (opens in a new tab)
- github.com/digitalbazaar/forge (opens in a new tab)
- github.com/digitalbazaar/forge/releases/tag/v1.4.1 (opens in a new tab)