dbcve.org
Improper Signature VerificationWeakness · CWE-347

CVE-2026-46684

CRITICAL · 9.5 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DataEase versions before 2.10.23 contain a JWT signature verification bypass in TokenUtils.validate(). The validation only checks token presence and length before passing to userBOByToken(token) which uses JWT.decode() without verifying the cryptographic signature. This allows attackers to forge tokens with arbitrary uid and oid values when licenseValid=true, effectively authenticating as any user.

MitigationUpgrade DataEase to version 2.10.23 or later which implements proper JWT signature verification. Until upgraded, consider implementing WAF rules to inspect and reject suspicious X-DE-TOKEN headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DataEase installation
    Check for running Java processes named 'dataease' or look for the DataEase installation directory, typically under /opt/dataease or /usr/local/dataease
    Affected if DataEase is not installed or not running
  2. Check DataEase version
    Run 'java -jar dataease.jar --version' or check the version file in the installation directory, then compare to the affected range (prior to 2.10.23)
    Affected if Installed version is lower than 2.10.23
  3. Verify TokenFilter is processing X-DE-TOKEN headers
    Inspect the web server or API gateway configuration for TokenFilter rules that process the X-DE-TOKEN header, typically found in dataease配置文件 or application.yml
    Affected if TokenFilter is active and processing X-DE-TOKEN requests without signature validation
  4. Check if licenseValid is enabled
    Examine the DataEase configuration file (application.yml or dataease.properties) for the licenseValid setting under authentication or security settings
    Affected if licenseValid is set to true in the configuration
  5. Verify TokenUtils.validate lacks signature verification
    Review the TokenUtils.java source code or decompiled class to confirm the validate() method calls JWT.decode() without signature verification (no verify() or decodeVerify() call)
    Affected if TokenUtils.validate() processes tokens without JWT signature verification

If DataEase version is below 2.10.23 AND the X-DE-TOKEN header processing is active AND licenseValid is enabled, the environment is vulnerable to authentication bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DataEase to version 2.10.23 or later which implements proper JWT signature verification. Until upgraded, consider implementing WAF rules to inspect and reject suspicious X-DE-TOKEN headers.

Recommended fix High confidence

2.10.23

  1. 1. Back up the current DataEase installation and its database before proceeding with any upgrade.
  2. 2. Identify the current DataEase version by checking the installation (typically via the UI or command line interface).
  3. 3. Confirm the current version is prior to 2.10.23 (vulnerable to CVE-2026-46684).
  4. 4. Download DataEase version 2.10.23 or a later stable release from the official DataEase repository or release channel.
  5. 5. Follow the standard DataEase upgrade procedure for your deployment method (Docker, Helm, or direct installation).
  6. 6. After upgrading, verify that the new version is running (2.10.23 or later).
  7. 7. Test authentication functionality to confirm token validation is working properly with signature verification enabled.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46684 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data