Vulnerability 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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/digitalbazaar/forge/commit/797c3f816a22748a96fceebb34eb3a6716
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-6wvx-3r32-xmcg
FAQ
What is CVE-2026-118777?
CVE-2026-118777 is a vulnerability with a CVSS score of 4.8 (MEDIUM). 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 header...
How severe is CVE-2026-118777?
CVE-2026-118777 has been rated MEDIUM with a CVSS base score of 4.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-118777?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.