Quick answers
- Is CVE-2026-82878 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82878 being exploited in the wild.
- How severe is CVE-2026-82878?
- 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-82878?
- A patch was published on 2026-07-25: Fix committed to GitHub; version 2.10.26 includes authorization checks Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82878 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82878?
- 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 is a missing object-level authorization check (CWE-639) in DataEase REST endpoints responsible for geographic information, dashboard linkage, and chart detail operations. Authenticated users can access resources by supplying arbitrary object identifiers in requests, bypassing authorization validation. The attack requires valid authentication credentials but no special privileges or user interaction. Attackers can read, modify, or delete map geometry and chart metadata, and reconfigure dashboard linkages for any resource in the system. The fix was merged on 2026-07-25 and is available in version 2.10.26 and later, as confirmed by GitHub commit 5fe46c4 which adds business-level permission checks (BusiPerCheckDTO).
Affected products
- DataEase DataEase before 2.10.26
Timeline
- 2026-08-31: disclosed: CVE-2026-82878 published on NVD
- 2026-07-25: patched: Fix committed to GitHub; version 2.10.26 includes authorization checks