Quick answers
- Is CVE-2026-82879 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82879 being exploited in the wild.
- How severe is CVE-2026-82879?
- Medium severity, with a CVSS score of 6.3, published 31 August 2026.
- Which products and versions are affected?
- DataEase before 2.10.26.
- Is there a fix for CVE-2026-82879?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82879 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82879?
- Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability consists of multiple authorization flaws in the sharing module: (1) Share tickets are not validated against the target share UUID, permitting ticket reuse across different shares; (2) the password-validation endpoint (POST /de2api/share/validate) issues LinkTokens without requiring a ticket, circumventing ticket-mandatory policies; (3) ticket creation and deletion endpoints lack ownership checks, allowing authenticated attackers to modify or delete tickets they do not own; (4) the share-enumeration endpoint (GET /de2api/share/queryRelationByUserId/{uid}) lacks authorization checks, exposing other users' share mappings. Network access and valid credentials are required; patches are available in version 2.10.26 and later.
Affected products
- DataEase DataEase before 2.10.26
Timeline
- 2026-08-31: disclosed