How severe is GHSA-554w-wpv2-vw27?

No CVSS score has been assigned to GHSA-554w-wpv2-vw27 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-554w-wpv2-vw27?

GHSA-554w-wpv2-vw27 affects the following packages: node-forge (npm). Ecosystems affected: npm.

How do I fix GHSA-554w-wpv2-vw27?

Update node-forge to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-554w-wpv2-vw27 is resolved across your whole dependency graph.

How do I detect GHSA-554w-wpv2-vw27 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-forge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-554w-wpv2-vw27 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-554w-wpv2-vw27 actively exploited in the wild?

No public exploit code has been indexed for GHSA-554w-wpv2-vw27 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-554w-wpv2-vw27?

GHSA-554w-wpv2-vw27 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-554w-wpv2-vw27?

GHSA-554w-wpv2-vw27 is classified as CWE-674 (CWE-674). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-554w-wpv2-vw27 published, and has it been updated?

GHSA-554w-wpv2-vw27 was published on November 26, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

node-forge has ASN.1 Unbounded RecursionGHSA-554w-wpv2-vw27

Fix: digitalbazaar/forge@260425c

GHSA-554w-wpv2-vw27 is a CWE-674 vulnerability in node-forge. A fix is available for node-forge — see the affected versions and patch details below.

Also known asCVE-2025-66031

Published

Nov 26, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-554w-wpv2-vw27.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

node-forgenpm

54.3Mdownloads / week

Description

Summary

An Uncontrolled Recursion (CWE-674) 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.

Details

An ASN.1 Denial of Service (Dos) vulnerability exists in the node-forge asn1.fromDer function within forge/lib/asn1.js. The ASN.1 DER parser implementation (_fromDer) recurses for every constructed ASN.1 value (SEQUENCE, SET, etc.) and lacks a guard limiting recursion depth. An attacker can craft a small DER blob containing a very large nesting depth of constructed TLVs which causes the Node.js V8 engine to exhaust its call stack and throw RangeError: Maximum call stack size exceeded, crashing or incapacitating the process handling the parse. This is a remote, low-cost Denial-of-Service against applications that parse untrusted ASN.1 objects.

Impact

This vulnerability enables an unauthenticated attacker to reliably crash a server or client using node-forge for TLS connections or certificate parsing.

This vulnerability impacts the ans1.fromDer function in node-forge before patched version 1.3.2.

Any downstream application using this component is impacted. These components may be leveraged by downstream applications in ways that enable full compromise of availability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-forge`	all versions	1.3.2`npm install node-forge@1.3.2`

Affected Products

1 product · 1 configurations

Application

forgedigitalbazaar

< 1.3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-forge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update node-forge to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-554w-wpv2-vw27 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-554w-wpv2-vw27 (CC BY 4.0)

Product	Fixed in	Advisory
Migration Toolkit for Virtualization 2.9	`migration-toolkit-virtualization/mtv-console-plugin-rhel9:1769034026`	RHSA-2026:1248
Network Observability (NETOBSERV) 1.11.0	`network-observability/network-observability-console-plugin-compat-rhel9:1771227610`	RHSA-2026:2900
Red Hat Advanced Cluster Security 4.8	`advanced-cluster-security/rhacs-main-rhel8:1769615659`	RHSA-2026:1517
Red Hat Advanced Cluster Security 4.9	`advanced-cluster-security/rhacs-main-rhel8:1770250889`	RHSA-2026:2350
Red Hat Advanced Cluster Security 4.9	`advanced-cluster-security/rhacs-main-rhel8:1770074713`	RHSA-2026:2568
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/lightspeed-rhel9:1768889838`	RHSA-2026:1596
Red Hat Ceph Storage 8	`rhceph/grafana-rhel9:1770630607`	RHSA-2026:2737
Red Hat Developer Hub 1.7	`rhdh/rhdh-hub-rhel9:1.7.4-1767715042`	RHSA-2026:0261

Frequently Asked Questions

### Summary An Uncontrolled Recursion (CWE-674) 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. ### Details An ASN.1 Denial of Service (Dos) vulnerability exists in the node-forge `asn1.fromDer` function within `forge/lib/asn1.js`. The ASN.1 DER parser implementation (`_fromDer`) recurses for every constructed ASN.1 value (SEQUENCE, SET, etc.) and lacks a guard limiting recursio

O3 Security · Impact-Aware SCA

Is GHSA-554w-wpv2-vw27 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works