{"answers":{"affected":"2 open source packages ship an affected version, including financejs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-56571 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-56571 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56571 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."},"fix_prompt":"Check this codebase for CVE-2025-56571 and fix it if it is affected.\n\nWhat it is: CVE-2025-56571 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.\nExploitation: There is no known exploitation of CVE-2025-56571 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- financejs (npm): affected all versions up to 4.1.0; no fix listed\n- financejs (npm): affected all versions up to 4.1.0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-56571/ (Markdown: https://insights.sbomify.com/CVE-2025-56571/index.md)","id":"CVE-2025-56571","markdown":"https://insights.sbomify.com/CVE-2025-56571/index.md","name":"CVE-2025-56571","record":{"aliases":["GHSA-f8r4-mf27-rf7m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript financial library","requires_auth":"none","summary":"An attacker can cause application stalls or crashes in Finance.js by exploiting excessive CPU usage in the IRR function's recursion handling.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"finance.js","vendor":"ebradyjobory"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-834","name":"Excessive Iteration"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Finance.js vulnerable to DoS via the IRR function’s depth parameter","id":"CVE-2025-56571","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Finance.js vulnerable to DoS via the seekZero() parameter","id":"CVE-2025-56572"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.1.0"],"package":"financejs","purl":null,"source":"GHSA-f8r4-mf27-rf7m"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.1.0"],"package":"financejs","purl":"pkg:npm/financejs","source":"GHSA-f8r4-mf27-rf7m"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-56568"},"products":["n/a"],"published":"2025-09-30","related":[{"cvss_score":7.5,"headline":"Finance.js vulnerable to DoS via the seekZero() parameter","id":"CVE-2025-56572","kev_date_added":null,"published":"2025-09-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"An attacker can cause application stalls or crashes in Finance.js by exploiting excessive CPU usage in the IRR function's recursion handling.","url":"https://insights.sbomify.com/CVE-2025-56571/"}