CVE-2026-10291 — @enderfga/claw-orchestrat…
Fix: Enderfga/claw-orchestrator@3f970a9CVE-2026-10291 is a Uncontrolled Resource Consumption vulnerability in @enderfga/claw-orchestrator. A fix is available for @enderfga/claw-orchestrator — see the affected versions and patch details below.
Enderfga claw-orchestrator Session Grep Endpoint embedded-server.ts validateRegex redos
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.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-10291.
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, and reverse-dependency count shows how many other packages break if it stays unpatched.
@enderfga/claw-orchestratornpmDescription
A security vulnerability has been detected in Enderfga claw-orchestrator up to 3.7.0. The impacted element is the function validateRegex of the file claw-orchestrator/src/embedded-server.ts of the component Session Grep Endpoint. The manipulation of the argument body.pattern leads to inefficient regular expression complexity. The attack may be initiated remotely. Upgrading to version 3.7.1 is sufficient to resolve this issue. The identifier of the patch is 3f970a974c65a94555c25af9f2796f11315e4584. It is recommended to upgrade the affected component.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @enderfga/claw-orchestrator | all versions | 3.7.1npm install @enderfga/claw-orchestrator@3.7.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @enderfga/claw-orchestrator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @enderfga/claw-orchestrator to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-10291 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-2026-10291 in your dependencies?
Find it across npm, including transitive dependencies.