Chroma users keep filing bugs
4 posts from 3 people3d activeFading, +0 this week
Posts per day
The posts behind it
[BUG]There are multiple vulnerabilities in latest version of chromadb 1.5.9, which are getting added transitively to libraries like crewAI and impacting all the projects using crewai
### Description Vulnerability ID CVE-2026-45829 CVE-2026-45830 CVE-2026-45831 CVE-2026-45832 CVE-2026-45833 ### Steps to Reproduce Vulnerability ID CVE-2026-45829 CVE-2026-45830 CVE-2026-45831 CVE-2026-45832 CVE-2026-45833 ### Expected behavior A non-vulnerable version of crewAi...
[Bug]:There are multiple vulnerabilities in latest version of chromadb 1.5.9, which are getting added transitively to libraries like crewAI and impacting all the projects using crewai
### What happened? Vulnerability Id : CVE-2026-45830 , CVE-2026-45831, CVE-2026-45829, CVE-2026-45833, CVE-2026-45832 ### Versions Vulnerability Id : CVE-2026-45830 , CVE-2026-45831, CVE-2026-45829, CVE-2026-45833, CVE-2026-45832 ### Relevant log output
Intermittent SIGSEGV in chromadb_rust_bindings on macOS ARM64
I am investigating intermittent native crashes with an existing local persistent index. I cannot share the database or source documents. I do not have a minimal reproducer or an established cause. Recorded environment: - macOS 27.0.1, ARM64 - Homebrew Python 3.14.6 - chromadb...
[Bug]: conditional get(ids=..., limit/offset) marks unreturned ids as known-absent, so a later add of an existing id commits and is silently dropped
### What happened? In a conditional transaction, `get(ids=[...])` with a `limit` or `offset` marks every requested id that the server did not return as *known absent* - but with a limit/offset the server didn't return them because of the window, not because they don't exist. The...
Companies and products named
About this problem
Evidence
4 posts from 3 people in 2 places, about 1 a week over 35 days. Mostly on chroma-core/chroma, crewAIInc/crewAI. Tools named alongside: PyPI, SQLite.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Chroma that state a pain but match no known issue yet. First post Sep 23, 2026, latest Oct 27, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other Chroma problems
RAG on Chroma returns irrelevant or missing context
3 posts from 3 people on GitHub issues.
Chroma deprecations force unplanned migrations
2 posts from 2 people on GitHub issues. Unverified.
Chroma GPU access and drivers are painful
2 posts from 1 person on GitHub issues. Unverified.
History