{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-32821 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32821 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32821 is a high-severity missing authorization vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 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-32821 and fix it if it is affected.\n\nWhat it is: CVE-2026-32821 is a high-severity missing authorization vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 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-32821 in the wild and no public exploit code.\n\nAffected product: datacycle-engine dataCycle-CORE. 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-32821/ (Markdown: https://insights.sbomify.com/CVE-2026-32821/index.md)","id":"CVE-2026-32821","markdown":"https://insights.sbomify.com/CVE-2026-32821/index.md","name":"CVE-2026-32821","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"data management system","requires_auth":"low_privilege","summary":"Authenticated users can impersonate others to read or modify collections due to missing object-level authorization checks in the API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, any authenticated API user who has their own access token can ask the collection API to evaluate permissions as a different user by supplying `user_email`. If the target user has collections, this can expose those collections through the API. In V4, once a collection id is known, the same controller also offers `add_item` and `remove_item` routes without any object-level `authorize!` checks,\ncreating a likely cross-user modification path. This is patched in version 26.06.08.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"API Collection Impersonation Via user_email And Missing Object- Level Authorization","id":"CVE-2026-32821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"dataCycle Unauthenticated Reflected DOM XSS Via flash[...] On Public Pages","id":"CVE-2026-32822"},"packages":[],"prev":{"headline":"dataCycle Public Markdown Path Traversal Via /docs/*path","id":"CVE-2026-32820"},"products":["dataCycle-CORE"],"published":"2026-07-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-20","vendors":["datacycle-engine"]},"summary":"Authenticated users can impersonate others to read or modify collections due to missing object-level authorization checks in the API.","url":"https://insights.sbomify.com/CVE-2026-32821/"}