# CVE-2026-125333: Forge: ReDoS in forge.http response header and cookie trimming


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-6cv4-p8m7-4r25, MINI-8x28-33vr-mgx4, MINI-96pw-3cc8-6xg5, MINI-9c9c-6m6v-vjqg, MINI-9f45-gj54-j65q, MINI-jf2p-5wjj-3548, MINI-xh5x-fm94-74rc, UBUNTU-CVE-2026-125333

## What is CVE-2026-125333?

CVE-2026-125333 is a medium-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 

### Official description

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. From 0.1.2 until 1.4.3, forge.http uses _trimString() in lib/http.js to remove trailing whitespace from response header values and cookie names and values with a regular expression that can take quadratic time. A malicious server or on-path attacker can supply a long whitespace run followed by a non-whitespace character in a response header, causing response.readHeader() or response.getCookies() to repeatedly scan the input and block the Node.js event loop or browser tab for minutes. Applications are affected only when they use forge.http with a socket pool to communicate with an untrusted server; forge.http is not loaded by require('node-forge'), and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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

1 open source package ship an affected version, including node-forge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-forge` | npm | From 0.1.2 | 1.4.3 |

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

Upgrade node-forge to 1.4.3 or later.

## Is CVE-2026-125333 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125333 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125333 is a medium-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125333 exists.

Affected packages and fixed versions:
- node-forge (npm): affected from 0.1.2; fixed in 1.4.3

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-125333/ (Markdown: https://insights.sbomify.com/CVE-2026-125333/index.md)
```

## Sources

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

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