CVE-2026-104142
waiting for further signalsZero needs more public information before it can validate it.GHSA-gcr3-cj2q-gj4q ↗EUVD-2026-101555 ↗
description
DataEase versions earlier than 2.10.26 allow authenticated users to save unsafe values in group-field binning definitions. When a chart uses the affected field, those values can cause unintended SQL to run against the configured backend database, risking data confidentiality, integrity, and availability.
mitigation
Upgrade DataEase to version 2.10.26 or later. Restrict access to users who can create or modify dataset group-field binning settings until the upgrade is complete.
fixed in 2.10.26
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-14 18:42Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-104142
{ "etk_id": "ETK-2026-1603", "cve_id": "CVE-2026-104142", "display_id": "CVE-2026-104142", "ghsa_id": "GHSA-gcr3-cj2q-gj4q", "euvd_id": "EUVD-2026-101555", "status": "published", "anchor_state": "anchored", "title": "Stored SQL injection in DataEase group-field binning", "summary": "DataEase versions earlier than 2.10.26 allow authenticated users to save unsafe values in group-field binning definitions. When a chart uses the affected field, those values can cause unintended SQL to run against the configured backend database, risking data confidentiality, integrity, and availability.", "mitigation": "Upgrade DataEase to version 2.10.26 or later. Restrict access to users who can create or modify dataset group-field binning settings until the upgrade is complete.", "vendor": "dataease", "product": "dataease", "affected": [ { "affected_notes": [], "affected_ranges": [ "<2.10.26" ], "ecosystem": "maven", "fixed_versions": [ "2.10.26" ], "package_name": "io.dataease", "purl": "pkg:maven/io.dataease" } ], "cwes": [ 89 ], "cvss_score": 8.7, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N", "epss_score": 0.0029, "epss_percentile": 0.1983, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 45.74440165, "t0_at": "2026-10-14T18:42:36.214000+00:00", "signals": { "trigger_signal": { "at": "2026-10-14T18:42:36.214000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-14T18:42:36.214000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-104142" } } }
published 2026-10-14 19:44Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.