How severe is CVE-2019-10775?

No CVSS score has been assigned to CVE-2019-10775 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2019-10775?

CVE-2019-10775 affects the following packages: ecstatic (npm). Ecosystems affected: npm.

How do I fix CVE-2019-10775?

Update ecstatic to 4.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10775 is resolved across your whole dependency graph.

How do I detect CVE-2019-10775 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecstatic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-10775 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2019-10775 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10775 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-10775?

CVE-2019-10775 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-10775?

CVE-2019-10775 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-10775 published, and has it been updated?

CVE-2019-10775 was published on December 15, 2020 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2019-10775 — ecstatic

CVE-2019-10775 is a Uncontrolled Resource Consumption vulnerability in ecstatic. A fix is available for ecstatic — see the affected versions and patch details below.

Denial of Service in ecstatic

Published

Dec 15, 2020

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

ecstaticnpm

335Kdownloads / week

Description

ecstatic have a denial of service vulnerability. Successful exploitation could lead to crash of an application.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ecstatic`	all versions	4.1.3`npm install ecstatic@4.1.3`

Affected Products

1 product · 1 configurations

Application

ecstaticecstatic_project

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecstatic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ecstatic to 4.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10775 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

ecstatic have a denial of service vulnerability. Successful exploitation could lead to crash of an application.

O3 Security · Impact-Aware SCA

Is CVE-2019-10775 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works