CVE-2026-50529
Unauthenticated token leak in DataEase share API allows access to protected shares.
Is CVE-2026-50529 being exploited?
Not confirmed. CVE-2026-50529 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-50529?
CVE-2026-50529 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50529?
Yes. A fix has been recorded for CVE-2026-50529. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50529 affect?
CVE-2026-50529 affects DataEase < 2.10.24, /de2api/share/proxyInfo endpoint, Share-related API (X-DE-LINK-TOKEN). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50529?
Upgrade to 2.10.24, rotate share tokens, restrict UUID exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Obtain valid X-DE-LINK-TOKEN for known share UUIDs, enabling unauthorized access or modification of shared data via share APIs.
Immediate action required
- affected< 2.10.24
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.