Medium

ASN.1 OID Integer Truncation in node-forge

IdentifiersCVE-2025-66030CWE-190· Integer Overflow or Wraparound

CVE-2025-66030 is an integer overflow/truncation vulnerability in Forge (node-forge) affecting versions 1.3.1 and earlier. When decoding ASN.1 Object Identifiers (OIDs), node-forge can process crafted OID arcs that exceed expected numeric bounds. Due to 32-bit bitwise truncation during decoding, oversized arcs may be interpreted as smaller, valid, and potentially trusted OID values. An attacker can supply malicious ASN.1/DER structures containing such oversized arcs so that downstream logic sees a different OID than the one actually encoded. This creates an interpretation flaw in OID handling that can undermine security decisions based on OID matching or validation. The issue is patched in node-forge 1.3.2, which hardens OID parsing and rejects parsed OID values larger than 232 - 1 and DER OID values larger than 253 - 1.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause downstream OID-based security checks to be bypassed. Any application that relies on node-forge's decoded OID values for trust decisions, cryptographic object classification, certificate or ASN.1 policy enforcement, or algorithm/extension identification may incorrectly accept attacker-controlled input as if it contained a trusted OID. The primary impact is integrity-related: misclassification of ASN.1 content and bypass of security controls predicated on exact OID identity.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, avoid trusting OID-based decisions derived from untrusted ASN.1/DER input processed by vulnerable node-forge versions. Where feasible, reject or pre-validate ASN.1 objects containing unusually large OID arc values before passing them to node-forge, and add independent verification of critical OIDs in higher-level application logic. Reducing exposure to attacker-supplied ASN.1/DER data lowers risk, but upgrading is the definitive fix.

Remediation

Patch, then assume compromise.

Upgrade node-forge to version 1.3.2 or later. The fixed release adds stricter OID parsing and rejects oversized OID values rather than allowing truncation-based reinterpretation. If node-forge is bundled transitively, update the dependent package set or product release that incorporates node-forge 1.3.2 or newer.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Digital BazaarForgeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

8 SOURCESView more in app

google security research pull requestsNews

Nov 26, 2025

Bump node-forge from 1.3.1 to 1.3.2 in /analysis/kernel/dashboard/frontend

A moderate-severity integer overflow/truncation vulnerability in node-forge 1.3.1 and below that can cause oversized OID arcs to be interpreted as smaller trusted OIDs, potentially bypassing OID-based security decisions.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4