CVE-2026-46684

CRITICALPre-NVD 9.59.5—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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
9.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.5Exploit: 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.23, DataEase enterprise token handling can let TokenFilter#doFilter() pass X-DE-TOKEN values to TokenUtils.validate(), which checks only token presence and length before userBOByToken(token) uses JWT.decode() without signature verification, allowing forged tokens with chosen uid and oid values to be accepted when licenseValid=true. This issue is fixed in version 2.10.23.

CVSS v3
9.5
EG Score
9.5(medium)
EG Risk
58(Track)
EG Risk 58/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity95% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
9.3%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 17, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Unauthorized Command Execution Vulnerability · Advisory · dataease/dataease · GitHub

Affected: v2.10.23.

https://github.com/dataease/dataease/security/advisories/GHSA-gp6v-f7mm-458v
github_release Patch Available

v2.10.23

Patch available: dataease/dataease v2.10.23

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

commit 3efda9d29c0d (dataease/dataease)

Fix landed in dataease/dataease commit 3efda9d29c0d — awaiting tagged release

https://github.com/dataease/dataease/commit/3efda9d29c0df4300d43bb7874638e03060c3e2d

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 12× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:17 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:37 UTCEG score recompute
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 19:45 UTCEG score recompute
  12. 2026-07-15 19:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46684?
CVE-2026-46684 is a critical vulnerability published on July 15, 2026. DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase enterprise token handling can let TokenFilter#doFilter() pass X-DE-TOKEN values to TokenUtils.validate(), which checks only token presence and length before userBOByToken(token) uses JWT.decode() without…
When was CVE-2026-46684 disclosed?
CVE-2026-46684 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46684 actively exploited?
CVE-2026-46684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46684?
CVE-2026-46684 has a CVSS v3 base score of 9.5 (NVD).
How do I remediate CVE-2026-46684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46684, 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-46684

Explore →

Is Your Infrastructure Affected by CVE-2026-46684?

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

Start Free Scan →Browse All CVEs