# CVE-2025-66031: node-forge ASN.1 Unbounded Recursion

> Remote attackers can cause Denial of Service via stack exhaustion by crafting deep ASN.1 structures in node-forge.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2025
- **Updated:** 28 Nov 2025
- **Also known as:** AZL-71134, CLEANSTART-2026-GS11212, CLEANSTART-2026-KB17672, DEBIAN-CVE-2025-66031, GHSA-554w-wpv2-vw27, MINI-2xx9-vpfh-7cr7, MINI-3f9f-gj6x-xx42, MINI-6gqj-28v8-77px, MINI-7m5w-jcw4-65g7, MINI-8xjc-674p-wm77, MINI-g369-9p2r-xg84, MINI-g43g-9mh3-fjmq, MINI-g4hc-rxvj-63pv, MINI-jqxj-wxrh-5g6w, MINI-m8w4-cwhg-vxhq, MINI-mrhw-vh2j-594c, MINI-pc3h-mxhr-q5vf, MINI-rm5g-qr59-9p3g, ROOT-APP-NPM-CVE-2025-66031, UBUNTU-CVE-2025-66031

## What is CVE-2025-66031?

CVE-2025-66031 is a high-severity denial of service vulnerability in digitalbazaar forge, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2025-66031?

2 open source packages ship an affected version, including node-forge. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-forge` | npm | All versions | 1.3.2 |
| `node-forge` | npm | All versions | 1.3.2 |

Products: Digitalbazaar Forge.

## How do I fix CVE-2025-66031?

Upgrade node-forge to 1.3.2 or later.

## Is CVE-2025-66031 being exploited?

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

## Other vulnerabilities in digitalbazaar forge

- [CVE-2020-7720](https://insights.sbomify.com/CVE-2020-7720/): Prototype Pollution (critical 9.8)
- [CVE-2025-12816](https://insights.sbomify.com/CVE-2025-12816/): CVE-2025-12816 (high 8.6)
- [CVE-2026-33891](https://insights.sbomify.com/CVE-2026-33891/): Forge has Denial of Service via Infinite Loop in BigInteger.modInverse() with Zero Input (high 7.5)
- [CVE-2026-33894](https://insights.sbomify.com/CVE-2026-33894/): Forge has signature forgery in RSA-PKCS due to ASN.1 extra field (high 7.5)
- [CVE-2026-33895](https://insights.sbomify.com/CVE-2026-33895/): Forge has signature forgery in Ed25519 due to missing S > L check (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66031 and fix it if it is affected.

What it is: CVE-2025-66031 is a high-severity denial of service vulnerability in digitalbazaar forge, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66031 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-forge (npm): affected all versions; fixed in 1.3.2
- node-forge (npm): affected all versions; fixed in 1.3.2

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

## Sources

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

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