Is CVE-2026-123991 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-123991 being exploited in the wild.

How severe is CVE-2026-123991?

High severity, with a CVSS score of 7.3, published 7 November 2026.

Is there a fix for CVE-2026-123991?

Yes: fixed in 2.10.28. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-123991 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-123991?

Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-123991: DataEase authentication filter unrestricted file upload

CVE-2026-123991 · Severity: high · CVSS 7.3 · Published 2026-11-07

DataEase is an open-source data visualization and dashboard platform. A flaw in its file upload authentication allows attackers to bypass security controls and upload arbitrary files to the server by manipulating the file argument in the authentication filter, potentially compromising system integrity and enabling code execution or data exfiltration.

Technologies: DataEase. Vendors: DataEase.

Quick answers

Is CVE-2026-123991 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123991 being exploited in the wild.
How severe is CVE-2026-123991?: High severity, with a CVSS score of 7.3, published 7 November 2026.
Which products and versions are affected?: DataEase up to 2.10.27.
Is there a fix for CVE-2026-123991?: Yes: fixed in 2.10.28. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123991 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-123991?: Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.10.28

Technical details

The vulnerability exists in the WhitelistUtils.endsWithAny function within the Authentication Filter component, where improper validation of file arguments allows an attacker to circumvent the URI suffix whitelist. The flaw enables unauthenticated remote file uploads. The fix enforces authentication on the standalone static-resource upload endpoint independently of the URI suffix whitelist.

Affected products

DataEase DataEase up to 2.10.27

Timeline

2026-11-07: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.