CVE-2026-45829

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 12.4%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: adp:redhat-sadp, epss
Elevated
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 12%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A pre-authentication, code injection vulnerability in version 1.0.0 or later of the ChromaDB Python project allows an unauthenticated attacker to run arbitrary code on the server by sending a malicious model repository and trust_remote_code set to true in the /api/v2/tenants/{tenant}/databases/{db}/collections endpoint.

CVSS v3
10.0
EG Score
10.0(medium)
EPSS
95.7%
KEV
Not listed

Published

May 18, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jul 15, 2026
Patch available. Sources: redhat.
redhat

2479623 – (CVE-2026-45829) CVE-2026-45829 chromadb: ChromaDB Python Project: Arbitrary code execution via pre-authentication code injection

https://bugzilla.redhat.com/show_bug.cgi?id=2479623
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-45829
generic

[Vulnerability ]: Python Backend Server Side RCE & Python Client SDK RCE · Issue #6717 · chroma-core/chroma · GitHub

https://github.com/chroma-core/chroma/issues/6717

Vendor Advisories for CVE-2026-45829(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipchromadbghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
chromadb1.0.0 ... 1.5.9 (44 versions)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 282 total refreshes for this CVE.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 21:09 UTCEG score recompute
  15. 2026-06-29 21:09 UTCGHSA enrichment
  16. 2026-06-28 12:31 UTCEG score recompute
  17. 2026-06-28 12:31 UTCGHSA enrichment
  18. 2026-06-28 08:00 UTCEG score recompute
  19. 2026-06-28 08:00 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 01:47 UTCEG score recompute
  23. 2026-06-28 01:47 UTCGHSA enrichment
  24. 2026-06-27 21:22 UTCEG score recompute
  25. 2026-06-27 21:22 UTCGHSA enrichment
Show 75 more
  1. 2026-06-27 12:52 UTCEG score recompute
  2. 2026-06-27 12:52 UTCGHSA enrichment
  3. 2026-06-27 07:44 UTCEG score recompute
  4. 2026-06-27 07:44 UTCGHSA enrichment
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 19:56 UTCEG score recompute
  7. 2026-06-26 19:56 UTCGHSA enrichment
  8. 2026-06-26 03:52 UTCEG score recompute
  9. 2026-06-26 03:52 UTCGHSA enrichment
  10. 2026-06-25 21:57 UTCEG score recompute
  11. 2026-06-25 21:57 UTCGHSA enrichment
  12. 2026-06-25 17:45 UTCEG score recompute
  13. 2026-06-25 17:45 UTCGHSA enrichment
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:26 UTCEPSS rescore
  23. 2026-06-19 19:26 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 02:21 UTCEG score recompute
  27. 2026-06-18 02:21 UTCGHSA enrichment
  28. 2026-06-17 20:13 UTCEG score recompute
  29. 2026-06-17 20:13 UTCGHSA enrichment
  30. 2026-06-17 17:53 UTCEPSS rescore
  31. 2026-06-17 13:15 UTCEG score recompute
  32. 2026-06-17 13:15 UTCGHSA enrichment
  33. 2026-06-17 06:02 UTCEG score recompute
  34. 2026-06-17 06:02 UTCGHSA enrichment
  35. 2026-06-17 01:49 UTCEG score recompute
  36. 2026-06-17 01:49 UTCGHSA enrichment
  37. 2026-06-16 21:37 UTCEG score recompute
  38. 2026-06-16 21:37 UTCGHSA enrichment
  39. 2026-06-16 17:52 UTCEPSS rescore
  40. 2026-06-16 11:49 UTCEG score recompute
  41. 2026-06-16 11:49 UTCGHSA enrichment
  42. 2026-06-16 07:34 UTCEG score recompute
  43. 2026-06-16 07:34 UTCGHSA enrichment
  44. 2026-06-16 03:23 UTCEG score recompute
  45. 2026-06-16 03:23 UTCGHSA enrichment
  46. 2026-06-15 23:10 UTCEG score recompute
  47. 2026-06-15 23:10 UTCGHSA enrichment
  48. 2026-06-15 17:49 UTCEPSS rescore
  49. 2026-06-15 04:16 UTCEG score recompute
  50. 2026-06-15 04:16 UTCGHSA enrichment
  51. 2026-06-15 00:05 UTCEG score recompute
  52. 2026-06-15 00:05 UTCGHSA enrichment
  53. 2026-06-14 19:53 UTCEG score recompute
  54. 2026-06-14 19:53 UTCGHSA enrichment
  55. 2026-06-14 15:41 UTCEG score recompute
  56. 2026-06-14 15:41 UTCGHSA enrichment
  57. 2026-06-14 11:28 UTCEG score recompute
  58. 2026-06-14 11:28 UTCGHSA enrichment
  59. 2026-06-14 07:16 UTCEG score recompute
  60. 2026-06-14 07:16 UTCGHSA enrichment
  61. 2026-06-14 03:05 UTCEG score recompute
  62. 2026-06-14 03:04 UTCGHSA enrichment
  63. 2026-06-13 23:00 UTCEPSS rescore
  64. 2026-06-13 22:52 UTCEG score recompute
  65. 2026-06-13 22:52 UTCGHSA enrichment
  66. 2026-06-13 14:54 UTCEG score recompute
  67. 2026-06-13 14:54 UTCGHSA enrichment
  68. 2026-06-13 06:40 UTCEG score recompute
  69. 2026-06-13 06:40 UTCGHSA enrichment
  70. 2026-06-13 02:22 UTCEG score recompute
  71. 2026-06-13 02:22 UTCGHSA enrichment
  72. 2026-06-12 23:12 UTCEPSS rescore
  73. 2026-06-12 23:12 UTCEPSS rescore
  74. 2026-06-12 22:11 UTCEG score recompute
  75. 2026-06-12 22:10 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-45829?
CVE-2026-45829 is a critical vulnerability published on May 18, 2026. A pre-authentication, code injection vulnerability in version 1.0.0 or later of the ChromaDB Python project allows an unauthenticated attacker to run arbitrary code on the server by sending a malicious model repository and trustremotecode set to true in the…
When was CVE-2026-45829 disclosed?
CVE-2026-45829 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45829 actively exploited?
CVE-2026-45829 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45829?
CVE-2026-45829 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-45829?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45829, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45829

Explore →

Is Your Infrastructure Affected by CVE-2026-45829?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.