CVE-2026-104142

waiting for further signalsZero needs more public information before it can validate it.

GHSA-gcr3-cj2q-gj4q ↗EUVD-2026-101555 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
dataease <2.10.26
fixed in 2.10.26
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1603Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:maven/io.dataease
7d 02h 08msince last run
46mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h48m
0
+4h
+6h
+8h
+10h
+12h

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

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%19th percentile
agent run time
46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 18:42Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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.

  1. 2026-10-14 18:42Z
    cve_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.1993,
  "epss_asof": "2026-10-21",
  "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 21:36Z

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.