CVE-2026-110593 MicroPyramid CVE debrief

Who should care

Defenders responsible for securing BottleCRM installations, particularly those with authenticated organization members, should assess exposure and prioritize remediation. They should review compensating controls for exposed systems, verify input validation and sanitization, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-110593 is a server-side template injection vulnerability in BottleCRM that allows authenticated organization members to disclose sensitive information or block the Celery worker. Defenders should assess exposure, prioritize remediation, and verify input validation and sanitization.

• Disclosure of rendering context and loaded Python modules
• Potential blocking of the shared Celery worker with nested loops
• Verification of input validation and sanitization
• Remediation priority for exposed installations

Technical summary

BottleCRM through 1.14.5 contains a server-side template injection vulnerability in the send_email Celery task. Authenticated organization members can submit template tags through POST /api/accounts/<id>/create_mail/ to disclose the rendering context and loaded Python modules, or block the shared Celery worker with nested loops. The vulnerability is caused by the use of django.template.Template() to compile user-supplied input without proper validation and sanitization. Defenders should review and restrict access to the send_email Celery task, validate and sanitize user-supplied input, and monitor for suspicious activity.

Defensive priority

Authenticated organization members can submit template tags to disclose the rendering context and loaded Python modules, or block the shared Celery worker with nested loops.

Recommended defensive actions

• Review and restrict access to the send_email Celery task
• Validate and sanitize user-supplied input to prevent template injection
• Monitor for suspicious activity and implement compensating controls
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the server-side template injection vulnerability in BottleCRM through 1.14.5. The vulnerability allows authenticated organization members to disclose sensitive information or block the Celery worker. Defenders should verify input validation and sanitization, and review compensating controls for exposed systems.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.