# CVE-2026-50529: DataEase: Link Token Leakage Prior to Share Password/Ticket Validation

> Unauthenticated attackers can obtain valid link tokens for protected shares by bypassing password validation, enabling unauthorized access to share-related APIs.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-7287-qqj9-phr6

## What is CVE-2026-50529?

CVE-2026-50529 is a high-severity authentication bypass vulnerability in dataease, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, the /de2api/share/proxyInfo share interface generates and returns X-DE-LINK-TOKEN before validating the share password or ticket, allowing unauthenticated attackers who know a protected share UUID to obtain a valid link token for subsequent share-related API calls even with missing or invalid credentials. This issue is fixed in version 2.10.24.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-50529 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50529 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50529 is a high-severity authentication bypass vulnerability in dataease, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50529 exists.

Affected product: dataease. 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-50529/ (Markdown: https://insights.sbomify.com/CVE-2026-50529/index.md)
```

## Sources

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

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