How severe is GHSA-9q64-mpxx-87fg?

No CVSS score has been assigned to GHSA-9q64-mpxx-87fg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9q64-mpxx-87fg?

GHSA-9q64-mpxx-87fg affects the following packages: ecstatic (npm), ecstatic (npm), ecstatic (npm). Ecosystems affected: npm.

How do I fix GHSA-9q64-mpxx-87fg?

Update ecstatic to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q64-mpxx-87fg is resolved across your whole dependency graph.

How do I detect GHSA-9q64-mpxx-87fg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecstatic. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9q64-mpxx-87fg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-9q64-mpxx-87fg?

O3 pinpoints whether GHSA-9q64-mpxx-87fg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9q64-mpxx-87fg actively exploited in the wild?

No public exploit code has been indexed for GHSA-9q64-mpxx-87fg 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.

When was GHSA-9q64-mpxx-87fg published, and has it been updated?

GHSA-9q64-mpxx-87fg was published on April 1, 2020 and was last updated on December 15, 2020. 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

GHSA-9q64-mpxx-87fg

GHSA-9q64-mpxx-87fg is a security vulnerability in ecstatic. O3 Security confirms whether GHSA-9q64-mpxx-87fg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Open Redirect in ecstatic

Published

Apr 1, 2020

Updated

Dec 15, 2020

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Dec 15, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs 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

284Kdownloads / week

Description

Versions of ecstatic prior to 4.1.2, 3.3.2 or 2.2.2 are vulnerable to Open Redirect. The package fails to validate redirects, allowing attackers to craft requests that result in an HTTP 301 redirect to any other domains.

Recommendation

If using ecstatic 4.x, upgrade to 4.1.2 or later. If using ecstatic 3.x, upgrade to 3.3.2 or later. If using ecstatic 2.x, upgrade to 2.2.2 or later.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ecstatic`	all versions	2.2.2
📦npm	`ecstatic`	≥ 3.0.0&&< 3.3.2	3.3.2
📦npm	`ecstatic`	≥ 4.0.0&&< 4.1.2	4.1.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ecstatic. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ecstatic to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q64-mpxx-87fg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9q64-mpxx-87fg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9q64-mpxx-87fg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `ecstatic` prior to 4.1.2, 3.3.2 or 2.2.2 are vulnerable to Open Redirect. The package fails to validate redirects, allowing attackers to craft requests that result in an `HTTP 301` redirect to any other domains. ## Recommendation If using `ecstatic` 4.x, upgrade to 4.1.2 or later. If using `ecstatic` 3.x, upgrade to 3.3.2 or later. If using `ecstatic` 2.x, upgrade to 2.2.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-9q64-mpxx-87fg in your dependencies?

O3 detects GHSA-9q64-mpxx-87fg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works