Skip to main content
VulnerabilityPublished

CVE-2025-64428: dataease · Injection

Affects dataeaseSource GCVE Database

0
Compare

Public exploit available · CVSS 8.9 High : upgrade to 2.10.17 as a priority.

Data as of 13 Nov 2026, 18:46 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.9
Patch
Available – fixed in 2.10.17
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade dataease/dataease to 2.10.17.

Affected software

ProductAffectedFixed in
GitHubdataease/dataeasepkg:github/dataease/dataeaseOther threatsAffected
  • <2.10.17
Fixed in
  • 2.10.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Dataease to version 2.10.17 or later, where the vulnerability is fully fixed. Versions prior to 2.10.17 remain vulnerable despite partial blacklist mitigations introduced in 2.10.14. No other mitigations are noted in the vendor advisory.

Description

Dataease versions prior to 2.10.17 are affected by a JNDI injection vulnerability (CWE-74). Although a blacklist was introduced in version 2.10.14, injection remains possible through specific URI schemes (iiop, corbaname, iiopname). This flaw allows remote attackers to perform injection attacks without authentication. The issue has been fixed in version 2.10.17.

References

Community reviews

Loading reviews…