Medium · CVSS 4.8CVE-2026-118777

Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-CookieCVE-2026-118777

Answer in brief

CVE-2026-118777 records a Medium severity (CVSS 4.8) vulnerability in Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie. The current sources do not mark it as known exploited. The current feed maps digitalbazaar/forge (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 29, 2026Updated Oct 29, 2026Source checked Oct 29, 2026First seen by HOL Oct 29, 2026Material review Oct 29, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 4.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 4.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps digitalbazaar/forge (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
digitalbazaar/forgegeneric	<1.4.1	1.4.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for digitalbazaar/forge.
Review the reported fix. Update digitalbazaar/forge to 1.4.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 29, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.