Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-5417: Server-Side Request Forgery in Dataease SQLbot

0
Medium
VulnerabilityCVE-2026-5417cvecve-2026-5417
Published: Thu Apr 02 2026 (04/02/2026, 18:15:11 UTC)
Source: CVE Database V5
Vendor/Project: Dataease
Product: SQLbot

Description

A vulnerability was determined in Dataease SQLbot up to 1.6.0. This issue affects the function get_es_data_by_http of the file backend/apps/db/es_engine.py of the component Elasticsearch Handler. This manipulation of the argument address causes server-side request forgery. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 1.7.0 is capable of addressing this issue. You should upgrade the affected component. The vendor was contacted early about this disclosure.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 19:37:41 UTC

Technical Analysis

CVE-2026-5417 is a server-side request forgery vulnerability identified in Dataease SQLbot, a tool used for SQL data operations, up to version 1.6.0. The vulnerability resides in the get_es_data_by_http function of the Elasticsearch Handler component (backend/apps/db/es_engine.py). Specifically, the function improperly handles the 'address' parameter, allowing an attacker to manipulate this input to induce the server to send crafted HTTP requests to arbitrary destinations. This SSRF flaw can be exploited remotely without user interaction but requires the attacker to have high privileges on the system, which limits the attack surface to some extent. The vulnerability could be leveraged to access internal services, bypass network restrictions, or perform reconnaissance within the victim’s infrastructure. Although no active exploits have been reported in the wild, the public disclosure of the vulnerability increases the risk of exploitation attempts. The vendor has addressed the issue in version 1.7.0, and upgrading is the recommended remediation. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:H means high privileges required, so this is a discrepancy to note), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability, resulting in a medium severity rating with a score of 5.1.

Potential Impact

The primary impact of this SSRF vulnerability is the potential for attackers with high privileges to coerce the vulnerable server into making unauthorized HTTP requests. This can lead to unauthorized internal network scanning, access to sensitive internal services, or exploitation of other vulnerabilities in internal systems that are not exposed externally. While the direct impact on confidentiality, integrity, and availability is rated low, the SSRF can serve as a pivot point for more severe attacks, including data exfiltration or lateral movement within an organization’s network. Organizations relying on Dataease SQLbot for database operations and Elasticsearch integration may face increased risk of internal network exposure if the vulnerability is exploited. The medium CVSS score reflects the moderate risk, considering the required privileges and the potential for indirect impacts. The absence of known active exploits reduces immediate risk but does not eliminate the threat, especially after public disclosure.

Mitigation Recommendations

To mitigate CVE-2026-5417, organizations should immediately upgrade Dataease SQLbot to version 1.7.0 or later, where the vulnerability has been fixed. In addition to patching, organizations should implement strict network segmentation and firewall rules to limit the server’s ability to make arbitrary outbound HTTP requests, especially to internal services. Employing web application firewalls (WAFs) with SSRF detection capabilities can help detect and block suspicious request patterns. Review and restrict the privileges of accounts running SQLbot to the minimum necessary, reducing the risk that an attacker can exploit this vulnerability. Conduct thorough logging and monitoring of outbound HTTP requests from the SQLbot server to identify anomalous activity. Finally, perform regular security assessments and penetration tests focusing on SSRF and internal network exposure to proactively identify and remediate similar issues.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-04-02T11:02:32.972Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69ceb81be6bfc5ba1df6dea1

Added to database: 4/2/2026, 6:40:27 PM

Last enriched: 4/2/2026, 7:37:41 PM

Last updated: 4/3/2026, 5:52:02 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses