Is CVE-2026-5417 exploited in the wild?

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

How severe is CVE-2026-5417?

Medium severity, with a CVSS score of 4.7, published 2 April 2026.

Is there a fix for CVE-2026-5417?

A patch was published on 2026-03-19: Version 1.7.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5417 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-5417?

Check whether you run DataEase SQLBot 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-5417: Dataease SQLbot SSRF in Elasticsearch Handler

CVE-2026-5417 · Severity: medium · CVSS 4.7 · Published 2026-04-02

Dataease SQLbot, a tool used for managing and querying databases, contains a security flaw in its Elasticsearch integration. An attacker could exploit this to force the server to make unauthorized requests to internal or external systems. This could lead to the exposure of internal network information or unauthorized access to private services, potentially disrupting operations or leaking sensitive data.

Technologies: DataEase SQLBot. Vendors: DataEase.

Quick answers

Is CVE-2026-5417 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5417 being exploited in the wild.
How severe is CVE-2026-5417?: Medium severity, with a CVSS score of 4.7, published 2 April 2026.
Which products and versions are affected?: DataEase SQLBot Up to 1.6.0.
Is there a fix for CVE-2026-5417?: A patch was published on 2026-03-19: Version 1.7.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5417 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-5417?: Check whether you run DataEase SQLBot 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.

Technical details

A server-side request forgery (SSRF) vulnerability exists in Dataease SQLbot versions up to 1.6.0. The flaw is located in the 'get_es_data_by_http' function within 'backend/apps/db/es_engine.py' of the Elasticsearch Handler component. By manipulating the 'address' argument, a remote attacker with high privileges can force the server to issue requests to arbitrary locations. This can be used to scan internal networks, bypass firewalls, or interact with internal services that are not otherwise accessible from the internet. The issue is addressed in version 1.7.0.

Affected products

Dataease SQLbot Up to 1.6.0

Timeline

2026-03-19: patched: Version 1.7.0 released
2026-04-02: disclosed: Initial public disclosure
2026-04-02: advisory: NVD publication date

References

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