CVE-2026-55631

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, the font management module allows authenticated users to submit an arbitrary fileTransName when creating a font record; when the record is later deleted, the backend concatenates that stored value with the font storage directory and passes it to FileUtils.deleteFile() without path traversal sanitization, allowing deletion of arbitrary writable files in the application container. This issue is fixed in version 2.10.24.

CVSS v3
7.2
EG Score
7.2(medium)
EPSS
23.3%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 8, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Path Traversal Leading to Arbitrary File Deletion via Font Management · Advisory · dataease/dataease · GitHub

Affected: v2.10.24.

https://github.com/dataease/dataease/security/advisories/GHSA-r99p-w8fc-93g6
github_release Patch Available

v2.10.24

Patch available: dataease/dataease v2.10.24

https://github.com/dataease/dataease/releases/tag/v2.10.24
github_commit

commit 8892a6945b0b (dataease/dataease)

Fix landed in dataease/dataease commit 8892a6945b0b — awaiting tagged release

https://github.com/dataease/dataease/commit/8892a6945b0b7a329a156155270fae58afa895bc

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 19:39 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 06:58 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 18:15 UTCEG score recompute
  8. 2026-07-14 05:33 UTCEG score recompute
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 16:51 UTCEG score recompute
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 04:09 UTCEG score recompute
  14. 2026-07-12 15:26 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 02:42 UTCEG score recompute
  17. 2026-07-11 14:00 UTCEG score recompute
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 01:16 UTCEG score recompute
  21. 2026-07-10 12:33 UTCEG score recompute
  22. 2026-07-09 23:51 UTCEG score recompute
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 11:10 UTCEG score recompute
Show 6 more
  1. 2026-07-08 22:27 UTCEG score recompute
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-08 09:45 UTCEG score recompute
  5. 2026-07-07 21:03 UTCEG score recompute
  6. 2026-07-07 21:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55631?
CVE-2026-55631 is a high vulnerability published on July 7, 2026. DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, the font management module allows authenticated users to submit an arbitrary fileTransName when creating a font record; when the record is later deleted, the backend concatenates that stored value with the font…
When was CVE-2026-55631 disclosed?
CVE-2026-55631 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55631 actively exploited?
CVE-2026-55631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55631?
CVE-2026-55631 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-55631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55631, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55631

Explore →

Is Your Infrastructure Affected by CVE-2026-55631?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.