CVE-2022-25885 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in hummus. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for hummus — see the affected versions and patch details below.
Denial of Service (DoS)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-25885.
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.
hummusnpmmuhammaranpmDescription
The package muhammara before 2.6.0 and the package hummus before 1.0.111 are vulnerable to Denial of Service (DoS) when PDFStreamForResponse() is used with invalid data.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | hummus | ≥ 1.0.0&&< 1.0.111 | 1.0.111npm install hummus@1.0.111 |
| 📦npm | muhammara | all versions | 2.6.0npm install muhammara@2.6.0 |
Affected Products
muhammaramuhammara_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hummus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hummus to 1.0.111 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25885 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 CVE-2022-25885 in your dependencies?
Find it across npm, including transitive dependencies.