CVE-2026-110595 json
BottleCRM 0.45 through 1.14.5 Memory Exhaustion via Contact and Case CSV Import
published 26d ago modified 14d ago also EUVD-2026-101223
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
BottleCRM 0.45 through 1.14.5 contains an uncontrolled memory allocation vulnerability in _read_upload() that reads entire CSV uploads before enforcing the 5 MB limit. Authenticated users with mass-import permission can send oversized CSV files concurrently to /api/contacts/import/ and /api/cases/import/ endpoints to exhaust worker memory and trigger out-of-memory termination.
Patch / fix
- micropyramid django_crm 1.14.10
Is CVE-2026-110595 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 14d ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/Django-CRM/Django-CRM/issues/828 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/aaronamran/CVE-Disclosures/tree/main/CVE-2026/CVE-2026-110595 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- MicroPyramid BottleCRM
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/Django-CRM/Django-CRM/issues/828
issue-tracking, exploit
-
github.com
/aaronamran/CVE-Disclosures/tree/main/CVE-2026/CVE-2026-110595
technical-description, exploit
-
github.com
/Django-CRM/Django-CRM/blob/v1.14.5/backend/contacts/import_views.py#L44
technical-description
-
github.com
/Django-CRM/Django-CRM/blob/v1.14.5/backend/cases/import_views.py#L44
technical-description
-
vulncheck.com
/advisories/bottlecrm-0.45-through-1.14.5-memory-exhaustion-via-contact-and-case-csv-import
third-party-advisory
Sources
- CVE List CVE-2026-110595
- NVD CVE-2026-110595
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.