cumulative-distribution-function Infinite Loop vulnerability
CVE-2021-29486GHSA-58qp-5328-v7mh
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (cumulative-distribution-function 2.0.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm cumulative-distribution-function
- Affected
- < 2.0.0
- Fixed in
- 2.0.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-58qp-5328-v7mh lists affected ranges: npm cumulative-distribution-function >=0 <2.0.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-58qp-5328-v7mh lists affected ranges: npm cumulative-distribution-function >=0 <2.0.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2021-29486: 1.98% estimated exploitation activity in the next 30 days; percentile 80.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact Apps using this library on improper data may crash or go into an infinite-loop In the case of a nodejs server-app using this library to act on invalid non-numeric data, the nodejs server may crash. This may affect other users of this server and/or require the server to be rebooted for proper operation. In the case of a browser app using this library to act on invalid non-numeric data, that browser may crash or lock up. A flaw enabling an infinite-loop was discovered in the code for evaluating the cumulative-distribution-function of input data. Although the documentation explains that numeric data is required, some users may confuse an array of strings like ["1","2","3","4","5"] for numeric data [1,2,3,4,5] when it is in fact string data. An infinite loop is possible when the cumulative-distribution-function is evaluated for a given point when the input data is string data rather than type number. This vulnerability enables an infinite-cpu-loop denial-of-service-attack on any…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-58qp-5328-v7mh
- Revision 1 · created ·
Published from osv record GHSA-58qp-5328-v7mh
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2021-29486 Advisory: cumulative-distribution-function Infinite Loop vulnerability IDs: CVE-2021-29486, GHSA-58qp-5328-v7mh Record: https://patchnext.com/advisories/cve-2021-29486 (revision 2, source checked 26 Oct 2026, 12:17 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: cumulative-distribution-function 2.0.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm cumulative-distribution-function: affected < 2.0.0; fixed in 2.0.0 ## Suggested inspection (read-only) - `npm ls cumulative-distribution-function --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on cumulative-distribution-function. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-58qp-5328-v7mh (OSV record GHSA-58qp-5328-v7mh lists affected ranges: npm cumulative-distribution-function >=0 <2.0.0 (fixed)) - Verified: https://github.com/advisories/GHSA-58qp-5328-v7mh (GitHub-reviewed advisory GHSA-58qp-5328-v7mh lists affected ranges: npm cumulative-distribution-function >=0 <2.0.0) Commands are suggestions: review each one before running it.
Loading voting…