# CVE-2026-82878: DataEase before 2.10.26 Missing Object-Level Authorization on Geographic, Linkage and Chart Endpoints

> Authenticated users can access, modify, or delete other users' geographic, linkage, and chart resources due to missing object-level authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-494p-38q6-9gx5, GHSA-v7cf-2ghm-9jxr

## What is CVE-2026-82878?

CVE-2026-82878 is a medium-severity missing authorization vulnerability in dataease, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DataEase versions before 2.10.26 omit object-level authorization checks on geographic information, dashboard linkage, and chart detail REST endpoints, allowing authenticated users to access resources belonging to other users. Attackers can overwrite or delete map geometry, modify dashboard linkages, and retrieve chart metadata and configuration for resources they do not own by supplying arbitrary identifiers in requests.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-82878 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82878 is a medium-severity missing authorization vulnerability in dataease, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82878 in the wild and no public exploit code.

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

## Sources

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

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