Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie (digitalbazaar forge)

CVE-2026-118777
MEDIUM 4.8

At a glance

Source
NVD
EPSS
EPSS 0.26 % · percentile 17 ()
State
PUBLISHED
Published
Updated
Assigner
GitHub_M
NVD status
Undergoing Analysis

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.

Weaknesses (CWE)

  • CWE-1321 — Improperly Controlled Modification of Object Prototype Attributes

References

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 4.8CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LGitHub_M
CVSS 3.1MEDIUM 4.8CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LNVD · security-advisories@github.com (Secondary)

European references

Affected products

ProductVersions
digitalbazaar · forgeaffected < 1.4.1

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD