@steipete/summarize is Vulnerable to Disk Exhaustion via Crafted Media ResponsesGHSA-q9xm-f36c-xm3q
MEDIUMFix: steipete/summarize#237GHSA-q9xm-f36c-xm3q is a medium-severity (CVSS 4.3) CWE-770 vulnerability in @steipete/summarize-core. A fix is available for @steipete/summarize-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-q9xm-f36c-xm3q.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@steipete/summarize-corenpmDescription
Summarize before 0.17.0 contains a resource exhaustion vulnerability that allows remote attackers to cause disk exhaustion by serving media responses that bypass the enforced size limit through missing or misreported Content-Length headers, chunked transfer encoding, or failed HEAD requests. Attackers who control a podcast feed or media URL can stream an unbounded response to local storage via the temp-file download path, exhausting disk or system resources on the host running the CLI.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @steipete/summarize-core | all versions | 0.17.0npm install @steipete/summarize-core@0.17.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @steipete/summarize-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @steipete/summarize-core to 0.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9xm-f36c-xm3q 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
Is GHSA-q9xm-f36c-xm3q in your dependencies?
Find it across npm, including transitive dependencies.