CVE-2026-110594 — BottleCRM 0.43 through 1.14.5 ReDoS via Case Routing Rule Regex
BottleCRM 0.43 through 1.14.5 contains a regular expression denial of service vulnerability that allows authenticated organization administrators to block web workers via unbounded routing rule regex patterns. Attackers can create a routing rule with a catastrophically backtracking pattern evaluated by _match_condition() during case saves, exhausting workers shared across all tenants.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (medium)+3
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (MicroPyramid BottleCRM).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| MicroPyramid | BottleCRM | ≥ 0.43 and ≤ 1.14.5 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 6.9 | CVSS 4.0 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 4.9 | CVSS 3.1 | Medium | 1.2 | 3.6 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 4.9 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.9 | CVSS 3.1 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-1333 · Inefficient Regular Expression Complexity (ReDoS)
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Source status changed · Received → Deferred
- Affected products added · micropyramid/bottlecrm
- Record published
- CVSS changed · 4.9
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 14, 2026 – Oct 16, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
6 on the record
- github.com/aaronamran/CVE-Disclosures/tree/main/CVE-2026/CVE-2026-110594
- github.com/Django-CRM/Django-CRM/issues/830
- github.com/advisories/GHSA-r225-9m2h-4x6v
- nvd.nist.gov/vuln/detail/CVE-2026-110594
- github.com/Django-CRM/Django-CRM/blob/v1.14.5/backend/cases/routing.py
- www.vulncheck.com/advisories/bottlecrm-0.43-through-1.14.5-redos-via-case-routing-rule-
Elsewhere on this site
Related CVEs (same products)
- Low CVE-2026-110592 BottleCRM 0.30 through 1.14.5 HTML Injection via Custom Invoice PDF Template 2d
- Medium CVE-2026-110593 BottleCRM through 1.14.5 Server-Side Template Injection via Account Email create_mail 2d
- Medium CVE-2026-110595 BottleCRM 0.45 through 1.14.5 Memory Exhaustion via Contact and Case CSV Import 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-110594 is "BottleCRM 0.43 through 1.14.5 ReDoS via Case Routing Rule Regex", rated Medium. It affects BottleCRM (MicroPyramid); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.9 describes technical severity. EPSS 0.62% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.