CVE-2026-45830

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-12. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection regardless of which tenant they belong to.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

June 12, 2026

Last Modified

July 31, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
No fix on record yet.
Web page

HiddenLayer SAI Security Advisory | ChromaDB

https://www.hiddenlayer.com/sai-security-advisory/2026-06-chromadb

Vendor Advisories for CVE-2026-45830(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
chromadb0.4.17 ... 1.5.9 (76 versions)
  • 0.4.17 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 10× in last 7d / 27× 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 260 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 160 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45830?
CVE-2026-45830 is a high-severity vulnerability; its CVE record was published on June 12, 2026. A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection regardless of which tenant they belong to.
When was the CVE record for CVE-2026-45830 published?
The CVE record for CVE-2026-45830 was published on June 12, 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 31, 2026; the record at its source may have been updated since.
Is CVE-2026-45830 actively exploited?
CVE-2026-45830 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45830?
CVE-2026-45830 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-45830?
No fix for CVE-2026-45830 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 vendor advisories EchelonGraph has for CVE-2026-45830 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-45830

Explore →

Is Your Infrastructure Affected by CVE-2026-45830?

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

Book a Demo →Browse All CVEs