Auth bypass in Datacycle-Engine Datacycle-Core
CVE-2026-32821
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, creating a likely cross-user modification path. This is patched in version 26.06.08.
EPSS: 0.004 (27.9th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
Affected products
- Datacycle-engine Datacycle-core — versions <= 25.07.3
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM)
Frequently asked questions
- What is CVE-2026-32821?
- CVE-2026-32821 is a high-severity vulnerability in Datacycle-Engine Datacycle-Core, classified under Improper Authorization. CVSS score: 8.1/10. Published 2026-07-20.
- How severe is CVE-2026-32821?
- High severity. CVSS v3 base score is 8.1 out of 10.