CVE-2026-32821
HighCVSS 8.1Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
In dataCycle-CORE before version 25.07.3, an authenticated API user can use their access token to query the collection API for permissions of another user by supplying their email. If the target user has collections, they may be exposed. In V4, a known collection can be modified via add/remove items without proper authorization.
Risk Assessment
The organization is at risk of unauthorized access to other users' data collections and unauthorized modification of those collections, potentially leading to data leakage or integrity loss.
Recommendation
Immediately update dataCycle-CORE to version 26.06.08 or later, which contains the fix for this vulnerability.
Other vulnerabilities in dataCycle-CORE
See all- CVE-2026-32825High
In dataCycle-CORE before version 25.07.3, there are no limits on login attempts via browser or API. Account locking is disabled and requests are not rate-limited, allowing continuous password guessing.
- CVE-2026-32824High
In dataCycle-CORE before version 25.07.3, an authenticated low-privileged API user can supply custom URLs in password reset or confirmation flows. These URLs are embedded in emails without host allowlisting.
- CVE-2026-32823Medium
In dataCycle-CORE before version 26.06.08, the application exposes server-side state changes through `GET` routes. Because browsers automatically send cookies on same-site top-level navigation and Rails does not apply CSRF protections to `GET`, an attacker can force a logged-in victim to modify application state by embedding a link, image, iframe, or redirect to one of these endpoints.
- CVE-2026-32820High
In dataCycle-CORE before version 25.07.3, the documentation and static Markdown renderer improperly handles attacker-controlled path segments. An unauthenticated attacker can use directory traversal sequences to read arbitrary .md files outside the intended docs or static directories.
- CVE-2026-32819Medium
In dataCycle-CORE before version 25.07.3, a Standard user can enumerate other users' names and email addresses through the /users/search endpoint, even though direct access to user profiles is denied.
- CVE-2026-32806High
Vulnerability in dataCycle-CORE before version 26.06.08 (including 25.07.3). The /remote_render endpoint does not restrict which partials can be rendered, allowing a low-privileged authenticated user to access server-side rendered admin content.
- CVE-2026-32822Medium
Reflected DOM XSS vulnerability in dataCycle-CORE before version 25.07.3. An unauthenticated attacker can inject arbitrary HTML into flash notifications on public routes, and the toast component injects that content into the DOM via innerHTML, allowing script execution via a crafted link.
- CVE-2026-32807High
Vulnerability in dataCycle-CORE before version 26.06.08 (including 25.07.3). Anyone with a DataLink UUID can fetch the attached text file directly, even if the link is expired, the caller is unauthenticated, or the normal show flow would have denied access.
Original NVD description (English source)
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.