# CVE-2026-32807: dataCycle Public DataLink Text File Download Ignores Validity And Authorization

> Unauthenticated attackers can access expired or restricted text file attachments via public DataLink UUIDs, exposing sensitive data.

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

## What is CVE-2026-32807?

CVE-2026-32807 is a high-severity missing authorization vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, 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, 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. Because the route is public and the mailer embeds the direct file URL, any leaked, forwarded, logged, or stale email link can continue to expose the attachment.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-32807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32807 is a high-severity missing authorization vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32807 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-32807/ (Markdown: https://insights.sbomify.com/CVE-2026-32807/index.md)
```

## Sources

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

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