Cross-user collection access via API authorization bypass
Published Jul 20, 2026 · Updated Jul 20, 2026
Authorization bypass in dataCycle CORE 25.07.3 and earlier allows remote authenticated users to read and modify other users' collections. The collection API trusts a caller-supplied user_email when evaluating permissions, and its V4 add_item and remove_item routes omit object-level authorize! checks. A valid API access token is required; disclosure follows when the impersonated account owns collections, while modification also requires a known collection ID.
Summary
What happened
Authorization bypass in dataCycle CORE 25.07.3 and earlier allows remote authenticated users to read and modify other users' collections. The collection API trusts a caller-supplied user_email when evaluating permissions, and its V4 add_item and remove_item routes omit object-level authorize! checks. A valid API access token is required; disclosure follows when the impersonated account owns collections, while modification also requires a known collection ID.
The record
- CVE
- CVE-2026-32821
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- dataCycle GmbH
- Product
- dataCycle CORE
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 25.07.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo