CVE-2026-45829

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-18. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (HiddenLayer, Inc.) lists ChromaDB versions 1.0.0 and later as affected. No release containing a fix is confirmed on record.

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.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 18, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Oct 15, 2026
No fix on record yet. Sources: redhat.
Web page

ChromaToast Served Pre-Auth

https://www.hiddenlayer.com/research/chromatoast-served-pre-auth
Red Hat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45829.json
Red Hat

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
Red HatMentions a patch (unverified)

CVE-2026-45829 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

[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 / EcosystemFix (by version range) / PatchReleasedSource
pipchromadb—ghsa

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 rangeFix by version rangeDependents
chromadb1.0.0 ... 1.5.9 (44 versions)
  • 1.0.0 through 1.5.9: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 342 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 242 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45829?
CVE-2026-45829 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-45829 published?
The CVE record for CVE-2026-45829 was published on May 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-45829 actively exploited?
CVE-2026-45829 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45829?
CVE-2026-45829 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45829?
No fix for CVE-2026-45829 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (HiddenLayer, Inc.) lists ChromaDB versions 1.0.0 and later as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-45829 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs