# CVE-2026-32819: dataCycle User Directory Enumeration Via /users/search

> A standard user can enumerate other users' names and email addresses via the search endpoint, leaking internal staff and external account details.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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-32819?

CVE-2026-32819 is a medium-severity 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, a Standard user can enumerate other users' names and email addresses through `/users/search`, even though direct access to those user profiles is denied. This leaks internal staff addresses, full names, and existence of guest and external test accounts.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-32819 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32819 is a medium-severity 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-32819 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-32819/ (Markdown: https://insights.sbomify.com/CVE-2026-32819/index.md)
```

## Sources

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

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