{"answers":{"affected":"3 open source packages ship an affected version, including chromadb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45831 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45831 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45831 is a high-severity missing authorization vulnerability in ChromaDB, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45831 and fix it if it is affected.\n\nWhat it is: CVE-2026-45831 is a high-severity missing authorization vulnerability in ChromaDB, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-45831 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- chromadb (PyPI): affected from 0.5.0 up to 1.5.9; no fix listed\n- chromadb (PyPI): affected from 0.5.0 up to 1.5.9; no fix listed\n- chromadb (PyPI): affected from 0.5.0 up to 1.5.9; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45831/ (Markdown: https://insights.sbomify.com/CVE-2026-45831/index.md)","id":"CVE-2026-45831","markdown":"https://insights.sbomify.com/CVE-2026-45831/index.md","name":"CVE-2026-45831","record":{"aliases":["GHSA-xph7-9rjv-w5fr","PYSEC-2026-3815"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ChromaDB vector database","requires_auth":"low_privilege","summary":"Attackers can perform cross-tenant actions in ChromaDB because the authorization provider fails to verify tenant, database, or collection scope for permissions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HiddenLayer","cpe":[{"product":"chromadb","vendor":"trychroma"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The SimpleRBACAuthorizationProvider authorization provider in versions 0.5.0 or later of the ChromaDB Python project evaluates whether a user holds a given permission but never checks which tenant, database, or collection that permission applies to allowing users to perform cross tenant actions.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to","id":"CVE-2026-45831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Auth bypass in ChromaDB","id":"CVE-2026-45832"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0.5.0"],"last_affected":["1.5.9"],"package":"chromadb","purl":null,"source":"GHSA-xph7-9rjv-w5fr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.5.0"],"last_affected":["1.5.9"],"package":"chromadb","purl":"pkg:pypi/chromadb","source":"GHSA-xph7-9rjv-w5fr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.5.0"],"last_affected":["1.5.9"],"package":"chromadb","purl":"pkg:pypi/chromadb","source":"PYSEC-2026-3815"}],"prev":{"headline":"ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection","id":"CVE-2026-45830"},"products":["ChromaDB"],"published":"2026-06-12","related":[{"cvss_score":9.4,"headline":"ChromaDB has a code injection vulnerability","id":"CVE-2026-45833","kev_date_added":null,"published":"2026-06-12"},{"cvss_score":8.8,"headline":"ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection","id":"CVE-2026-45830","kev_date_added":null,"published":"2026-06-12"},{"cvss_score":8.8,"headline":"Auth bypass in ChromaDB","id":"CVE-2026-45832","kev_date_added":null,"published":"2026-06-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-12","vendors":["Chroma"]},"summary":"Attackers can perform cross-tenant actions in ChromaDB because the authorization provider fails to verify tenant, database, or collection scope for permissions.","url":"https://insights.sbomify.com/CVE-2026-45831/"}