SSRF (Server-Side Request Forgery) in Dataease SQLbot (CVE-2026-5417)
Summary
SSRF in Dataease SQLbot (CVE-2026-5417). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-5417 has been found in Dataease SQLbot.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Dataease SQLbot CVE-2026-5417" on the vendor's site.
CVE-2026-5417 (Dataease SQLbot) — CWE-918 / CVSS v3 4.7
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Dataease SQLbot.
Check the vendor advisory for the affected versions of Dataease SQLbot.
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Dataease SQLbot を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- report vuldb.com
- report notion.so