# CVE-2025-56572: Finance.js vulnerable to DoS via the seekZero() parameter

> A remote attacker can cause a denial of service in the finance.js library via the seekZero() parameter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-5q7q-p8pc-782h

## What is CVE-2025-56572?

CVE-2025-56572 is a high-severity denial of service vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in finance.js v.4.1.0 allows a remote attacker to cause a denial of service via the seekZero() parameter.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including financejs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `financejs` | npm | All versions to 4.1.0 | None |
| `financejs` | npm | All versions to 4.1.0 | None |

Products: Ebradyjobory Finance.js.

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

No fix has been published for CVE-2025-56572 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56572 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-56571](https://insights.sbomify.com/CVE-2025-56571/): Finance.js vulnerable to DoS via the IRR function’s depth parameter (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56572 is a high-severity denial of service vulnerability in n/a, published on 30 Sep 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-56572 in the wild and no public exploit code.

Affected packages and fixed versions:
- financejs (npm): affected all versions up to 4.1.0; no fix listed
- financejs (npm): affected all versions up to 4.1.0; no fix listed

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

## Sources

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

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