{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45832 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45832 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45832 is a high-severity authentication bypass 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-45832 and fix it if it is affected.\n\nWhat it is: CVE-2026-45832 is a high-severity authentication bypass 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-45832 in the wild and no public exploit code.\n\nAffected product: ChromaDB. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-45832/ (Markdown: https://insights.sbomify.com/CVE-2026-45832/index.md)","id":"CVE-2026-45832","markdown":"https://insights.sbomify.com/CVE-2026-45832/index.md","name":"CVE-2026-45832","record":{"aliases":["GHSA-x97m-f58v-9cwg"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ChromaDB vector database","requires_auth":"low_privilege","summary":"Attackers can bypass authorization controls in ChromaDB by accessing V1 collection-level endpoints that incorrectly pass null tenant and database identifiers.","user_interaction":"not_required","vuln_class":"auth_bypass"},"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-551","name":"Incorrect Behavior Order: Authorization Before Parsing and Canonicalization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the authorization layer, allowing attackers to bypass authorization controls by using the V1 endpoints.","ecosystems":[],"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":"Auth bypass in ChromaDB","id":"CVE-2026-45832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ChromaDB has a code injection vulnerability","id":"CVE-2026-45833"},"packages":[],"prev":{"headline":"ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to","id":"CVE-2026-45831"},"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":"ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to","id":"CVE-2026-45831","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":"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-07-31","vendors":["Chroma"]},"summary":"Attackers can bypass authorization controls in ChromaDB by accessing V1 collection-level endpoints that incorrectly pass null tenant and database identifiers.","url":"https://insights.sbomify.com/CVE-2026-45832/"}