# CVE-2026-32821: API Collection Impersonation Via user_email And Missing Object- Level Authorization

> Authenticated users can impersonate others to read or modify collections due to missing object-level authorization checks in the API.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026

## What is CVE-2026-32821?

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.

### Official 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,
creating a likely cross-user modification path. This is patched in version 26.06.08.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-32821?


## How do I fix CVE-2026-32821?

No fix has been published for CVE-2026-32821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32821 being exploited?

There is no known exploitation of CVE-2026-32821 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32821 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-32821 in the wild and no public exploit code.

Affected product: datacycle-engine dataCycle-CORE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32821/ (Markdown: https://insights.sbomify.com/CVE-2026-32821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32821
- OSV: https://osv.dev/vulnerability/CVE-2026-32821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32821/
Summaries are generated and may contain mistakes; the official description above is the record.