chromadb 1.5.9
PkgFire would stop this release from installing.·Checked 1 hour ago·Published 5 May 2026
Why
-
blockLikely exploited
ChromaDB Python project has a pre-authentication code injection vulnerability EPSS puts the chance of exploitation in the next 30 days at 15% (higher than 97% of all scored vulnerabilities). That is a forecast, not an observation, so it raises this finding rather than blocking it.
-
blockVulnerability
ChromaDB has a code injection vulnerability
-
blockVulnerability
ChromaDB has a code injection vulnerability
-
blockLikely exploited
ChromaDB Python project has a pre-authentication code injection vulnerability EPSS puts the chance of exploitation in the next 30 days at 15% (higher than 97% of all scored vulnerabilities). That is a forecast, not an observation, so it raises this finding rather than blocking it.
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- None, and no earlier version had any
Licence and upkeep
- Licence
- non-standard
- Source
- github.com/chroma-core/chroma ↗
- OpenSSF Scorecard
- 5.1 / 10
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.