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


- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-118777?

CVE-2026-118777 is a medium-severity vulnerability in digitalbazaar forge, published on 29 Oct 2026. 

### 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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-118777?


## How do I fix CVE-2026-118777?

No fix has been published for CVE-2026-118777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118777 being exploited?

There is no known exploitation of CVE-2026-118777 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118777 and fix it if it is affected.

What it is: CVE-2026-118777 is a medium-severity vulnerability in digitalbazaar forge, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118777 in the wild and no public exploit code.

Affected product: digitalbazaar forge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118777/ (Markdown: https://insights.sbomify.com/CVE-2026-118777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118777
- OSV: https://osv.dev/vulnerability/CVE-2026-118777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118777/
Summaries are generated and may contain mistakes; the official description above is the record.