LiveActive security incident?Get immediate response
CVE Record

CVE-2025-56571: Finance.js v4.1.0 contains a Denial of Service (DoS) vulnerability via the IRR function’s depth parameter.

Finance.js v4.1.0 contains a Denial of Service (DoS) vulnerability via the IRR function’s depth parameter. Improper handling of the recursion/iteration limit can lead to excessive CPU usage, causing application stalls or crashes.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-56571 is a reported denial-of-service issue in Finance.js v4.1.0. If an application exposes the IRR calculation to untrusted input, excessive recursion or iteration can consume CPU and stall or crash the service. The source bundle does not name a fixed version.

Executive priority

Treat this as a high-priority availability risk if Finance.js v4.1.0 supports customer-facing financial calculations. Prioritize inventory, input control, and vendor guidance review before assuming a patch path exists.

Technical view

The issue is described as CWE-834: excessive iteration in Finance.js v4.1.0 IRR handling through the depth parameter. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges, no user interaction, availability impact only.

Likely exposure

Exposure is most likely in Node.js or browser applications using Finance.js v4.1.0 where users can influence IRR inputs, especially the depth parameter or calculation workload. The CVE affected-product fields are incomplete, so inventory confirmation is required.

Exploitation context

The CVE is not listed as KEV in the source bundle. Public references include the project, source snapshot, CVE records, and a Medium write-up. No cited source in the bundle establishes active exploitation.

Researcher notes

The strongest evidence is CVE metadata and referenced project/source material. The affected-product fields are marked n/a, and the bundle does not identify a patched version. Avoid overclaiming exploit activity or exact remediation beyond input hardening and vendor follow-up.

Mitigation direction

  • Inventory Finance.js usage and confirm whether v4.1.0 is present.
  • Check vendor or project guidance for a fixed release or official workaround.
  • Block untrusted control of IRR depth and validate calculation inputs.
  • Apply service-level rate limits and timeouts around exposed calculation endpoints.
  • Monitor CPU saturation, request latency, and crashes tied to IRR workflows.

Validation and detection

  • Search manifests and lockfiles for Finance.js v4.1.0.
  • Trace application routes or jobs that call the IRR function.
  • Confirm whether external users can influence IRR depth or workload.
  • Run only controlled nonproduction tests for CPU stalls with abnormal inputs.
  • Review logs and APM for repeated expensive financial-calculation requests.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-834: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-56571 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-56571Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-834 · source CWE mapping

Excessive Iteration

Excessive Iteration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.