Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Forge: ReDoS in forge.http response header and cookie trimming

CVSS 3.1 5.9 MEDIUMCheck source for fixed versionsKEV status unknown

Historical advisory recorded 10 Nov 2026 23:21:22 UTC. Read the latest advisory.

cve-program · CVE-2026-125333

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-125333

Published

forge

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "digitalbazaar",
                    "product": "forge",
                    "versions": [
                        {
                            "version": ">= 0.1.2, < 1.4.3",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 09:53 UTC · 273 of 275 readable · 251 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current