CVE-2025-58451 — cattown
Fix: IEatUranium238/Cattown@70c2a28CVE-2025-58451 is a Uncontrolled Resource Consumption vulnerability in cattown. A fix is available for cattown — see the affected versions and patch details below.
Cattown Vulnerable to Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2025-58451.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
cattownnpmDescription
Overview
A security review of the Cattown identified multiple weaknesses that could potentially impact its stability and security.
Affected Versions
- All versions below 1.0.2
Description of Vulnerabilities
- CWE-1333: Inefficient Regular Expression Complexity The package used regular expressions with inefficient, potentially exponential worst-case complexity. This can cause excessive CPU usage due to excessive backtracking on crafted inputs, potentially leading to denial of service.
- CWE-400: Uncontrolled Resource Consumption (Resource Exhaustion) The package was vulnerable to resource exhaustion, where processing malicious inputs could cause high CPU or memory usage, potentially leading to denial of service.
Impact
- Trigger excessive CPU consumption leading to denial of service
- Cause resource exhaustion affecting service availability
- Bypass protection mechanisms causing unexpected or insecure behavior
Resolution
These vulnerabilities have been fixed in version 1.0.2 of the Cattown. Users are strongly encouraged to upgrade to this version to mitigate the risks.
Recommendations
- Upgrade to Cattown version 1.0.2 or later as soon as possible.
- Review and restrict input sources if untrusted inputs are processed.
Acknowledgments
The issues were proactively identified through CodeQL static analysis.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | cattown | all versions | 1.0.2npm install cattown@1.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cattown, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cattown to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58451 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-2025-58451 in your dependencies?
Find it across npm, including transitive dependencies.