CVE-2026-123990

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

GHSA-54vg-4hhr-cfwh ↗EUVD-2026-119316 ↗

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.0; 2.10.1; 2.10.2; 2.10.3; 2.10.4; 2.10.5; 2.10.6; 2.10.7; 2.10.8; 2.10.9; 2.10.10; 2.10.11; 2.10.12; 2.10.13; 2.10.14; 2.10.15; 2.10.16; 2.10.17; 2.10.18; 2.10.19; 2.10.20; 2.10.21; 2.10.22; 2.10.23; 2.10.24; 2.10.25; 2.10.26; 2.10.27; 3.0; 3.1.0
ETK-2026-3858Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 48msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h36m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

DataEase releases through 2.10.27 and 3.1.0 contain an SQL injection flaw in the Chart Data Handler. A remote attacker may influence database queries when they can supply the affected operator input to that handler.

mitigation

Upgrade DataEase to version 3.2.0. Restrict untrusted access to chart-data functionality until the upgrade is complete.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-07 16:30Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-07 16:30Z
    ghsa: trigger signal, started the run
  2. 2026-11-07 16:30Z

this entry in the feed

GET /api/v1/feed/CVE-2026-123990

{
  "etk_id": "ETK-2026-3858",
  "cve_id": "CVE-2026-123990",
  "display_id": "CVE-2026-123990",
  "ghsa_id": "GHSA-54vg-4hhr-cfwh",
  "euvd_id": "EUVD-2026-119316",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in DataEase Chart Data Handler",
  "summary": "DataEase releases through 2.10.27 and 3.1.0 contain an SQL injection flaw in the Chart Data Handler. A remote attacker may influence database queries when they can supply the affected operator input to that handler.",
  "mitigation": "Upgrade DataEase to version 3.2.0. Restrict untrusted access to chart-data functionality until the upgrade is complete.",
  "vendor": null,
  "product": "DataEase",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.10.0",
        "2.10.1",
        "2.10.2",
        "2.10.3",
        "2.10.4",
        "2.10.5",
        "2.10.6",
        "2.10.7",
        "2.10.8",
        "2.10.9",
        "2.10.10",
        "2.10.11",
        "2.10.12",
        "2.10.13",
        "2.10.14",
        "2.10.15",
        "2.10.16",
        "2.10.17",
        "2.10.18",
        "2.10.19",
        "2.10.20",
        "2.10.21",
        "2.10.22",
        "2.10.23",
        "2.10.24",
        "2.10.25",
        "2.10.26",
        "2.10.27",
        "3.0",
        "3.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DataEase",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 23.5523896,
  "t0_at": "2026-11-07T16:30:16.974000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-07T16:30:16.974000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T16:30:16.974000+00:00",
      "url": "https://github.com/advisories/GHSA-54vg-4hhr-cfwh"
    }
  }
}

published 2026-11-07 18:42Z
last change 2026-11-08 00:08Z

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.