CVE-2026-32137
SQL injection in DataEase API allows RCE via tableName.
Is CVE-2026-32137 being exploited?
Not confirmed. CVE-2026-32137 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-32137?
CVE-2026-32137 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32137?
Yes. A fix has been recorded for CVE-2026-32137. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32137 affect?
CVE-2026-32137 affects DataEase (pre-2.10.20). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32137?
Upgrade to DataEase 2.10.20+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via unparameterized SQL; attacker can execute arbitrary SQL by crafting tableName, risking data theft/compromise.
Patch when possible
- affected< 2.10.20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.