High · CVSS 8.7CVE-2026-104143

DataEase: Stored SQL Injection via dateFormat field templatesCVE-2026-104143

Answer in brief

CVE-2026-104143 records a High severity (CVSS 8.7) vulnerability in DataEase: Stored SQL Injection via dateFormat field templates. The current sources do not mark it as known exploited. The current feed maps dataease/dataease (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 14, 2026Updated Oct 14, 2026Source checked Oct 14, 2026First seen by HOL Oct 14, 2026Material review Oct 14, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps dataease/dataease (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
dataease/dataeasegeneric	<2.10.26	2.10.26

Recommended response

Check inventory. Check lockfiles and deployed manifests for dataease/dataease.
Review the reported fix. Update dataease/dataease to 2.10.26 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 14, 2026

Sources and claim methodology

Upstream source description

DataEase is an open source data visualization and analysis tool. Prior to 2.10.26, authenticated users can store a crafted custom dateFormat for a dataset field. DatasetTableFieldDTO.dateFormat is inserted without validation into date conversion templates used by Dimension2SQLObj, CustomWhere2Str, Field2SQLObj, WhereTree2Str, and ExtWhere2Str. When a chart renders the field on a cross-datasource dataset, Calcite parsing is bypassed and the crafted format can directly alter the generated SQL. On a single-datasource dataset, exploitation additionally requires the payload to survive Calcite reserialization as a valid string literal. Successful exploitation can compromise the confidentiality, integrity, and availability of the backend database. This issue is fixed in version 2.10.26.

Quoted source text, attributed separately from HOL analysis.