Description
DataEase before 2.10.26 contains multiple access control defects in the sharing link module. Tickets are not bound to the target share UUID, so a valid ticket issued for one share can be reused against another (ShareTicketManage.validateTicket / POST /de2api/share/proxyInfo). The POST /de2api/share/validate endpoint issues a LinkToken after password verification without requiring a ticket, bypassing the 'ticket mandatory' policy. Additionally, the ticket create and delete endpoints (POST /de2api/ticket/saveTicket, POST /de2api/ticket/delTicket) lack share-ownership checks, allowing an authenticated user who knows another user's ticket to modify, rebind, or delete it (denial of service), and GET /de2api/share/queryRelationByUserId/{uid} allows authenticated users to enumerate other users' share mappings.
Published: 2026-08-31
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized data access via share ticket reuse
Action: Patch Now
AI Analysis

Impact

DataEase versions prior to 2.10.26 contain an access control defect in the sharing link module where tickets are not bound to the intended share UUID. A valid ticket issued for one share can be replayed against another, allowing an attacker to obtain a LinkToken and effectively bypass the intended security boundary. The flaw also lets a user who knows another’s ticket modify, rebind, or delete it, and enables enumeration of share relations. The weakness is classified as CWE‑863, reflecting a flaw in authorization checks.

Affected Systems

All installations of DataEase version 2.10.25 and earlier. The vulnerability affects the share ticket endpoints provided by the dataease:dataease product. Users running the operating warehouse or dashboard services without the 2.10.26 patch are susceptible. No other vendors or product lines are listed as affected.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity due to limited impact beyond the share privileges. EPSS data is not available, and the issue is not listed in CISA’s KEV catalog, suggesting that widespread exploitation has not been observed yet. Exploitation requires authentication to the target instance, meaning an attacker must compromise or obtain valid user credentials or possess a legitimate ticket from another user. Once authenticated, the attacker can reuse a ticket against a different share, elevate access rights, or cause denial of service by deleting other users’ tickets. The absence of strict ownership checks opens the path for this misuse.

Generated by OpenCVE AI on August 31, 2026 at 13:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to DataEase 2.10.26 or later to receive the official fix that binds tickets to share UUIDs and enforces ownership checks on ticket‑creation and ticket‑deletion endpoints
  • Restrict the /de2api/share/proxyInfo, /de2api/share/validate, and ticket creation/deletion endpoints to privileged roles only, and verify that proper role checks are enforced in configuration or code.
  • Implement monitoring of share ticket usage and enforce automatic revocation of tickets after a short validity period or after a successful view to reduce the window for replay attacks.

Generated by OpenCVE AI on August 31, 2026 at 13:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 31 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 31 Aug 2026 11:00:00 +0000

Type Values Removed Values Added
Description DataEase before 2.10.26 contains multiple access control defects in the sharing link module. Tickets are not bound to the target share UUID, so a valid ticket issued for one share can be reused against another (ShareTicketManage.validateTicket / POST /de2api/share/proxyInfo). The POST /de2api/share/validate endpoint issues a LinkToken after password verification without requiring a ticket, bypassing the 'ticket mandatory' policy. Additionally, the ticket create and delete endpoints (POST /de2api/ticket/saveTicket, POST /de2api/ticket/delTicket) lack share-ownership checks, allowing an authenticated user who knows another user's ticket to modify, rebind, or delete it (denial of service), and GET /de2api/share/queryRelationByUserId/{uid} allows authenticated users to enumerate other users' share mappings.
Title DataEase before 2.10.26 Access Control Bypass via Share Tickets
First Time appeared Dataease
Dataease dataease
Weaknesses CWE-863
CPEs cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:*
Vendors & Products Dataease
Dataease dataease
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}

cvssV4_0

{'score': 5.3, 'vector': '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'}


Subscriptions

Dataease Dataease
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-31T18:51:31.680Z

Reserved: 2026-08-31T08:38:43.268Z

Link: CVE-2026-82879

cve-icon Vulnrichment

Updated: 2026-08-31T16:23:04.946Z

cve-icon NVD

Status : Deferred

Published: 2026-08-31T11:16:41.603

Modified: 2026-09-08T20:18:59.270

Link: CVE-2026-82879

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-31T13:30:04Z

Weaknesses