{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82879 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82879 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82879 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."},"fix_prompt":"Check this codebase for CVE-2026-82879 and fix it if it is affected.\n\nWhat it is: CVE-2026-82879 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.\nExploitation: There is no known exploitation of CVE-2026-82879 in the wild and no public exploit code.\n\nAffected product: dataease. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82879/ (Markdown: https://insights.sbomify.com/CVE-2026-82879/index.md)","id":"CVE-2026-82879","markdown":"https://insights.sbomify.com/CVE-2026-82879/index.md","name":"CVE-2026-82879","record":{"aliases":["GHSA-9h54-39gh-5qfg","GHSA-p7cf-5v9w-9rvj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"DataEase BI platform","requires_auth":"low_privilege","summary":"Attackers can bypass share access controls to read unauthorized data or disrupt sharing features by exploiting missing ownership checks and ticket validation flaws.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DataEase before 2.10.26 Access Control Bypass via Share Tickets","id":"CVE-2026-82879","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"YaCy Search Server through 1.941 XML External Entity Injection via Parsers","id":"CVE-2026-82880"},"packages":[],"prev":{"headline":"DataEase before 2.10.26 Missing Object-Level Authorization on Geographic, Linkage and Chart Endpoints","id":"CVE-2026-82878"},"products":["dataease"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["dataease"]},"summary":"Attackers can bypass share access controls to read unauthorized data or disrupt sharing features by exploiting missing ownership checks and ticket validation flaws.","url":"https://insights.sbomify.com/CVE-2026-82879/"}