Loading...
Skip to main content

CVE-2025-54379 — Vulnerability in github.com/lf-edge/ekuiper — CVE...

HIGH

eKuiper API endpoints handling SQL queries with user-controlled table names.

Published July 24, 2025Updated September 10, 2026Source: osv

Summary

### Summary A critical SQL Injection vulnerability exists in the `getLast` API functionality of the eKuiper project. This flaw allows unauthenticated remote attackers to execute arbitrary SQL statements on the underlying SQLite database by manipulating the table name input in an API request. Exploitation can lead to data theft, corruption, or deletion, and full database compromise. ### Details The root cause lies in the use of unsanitized user-controlled input when constructing SQL queries using `fmt.Sprintf`, without validating the `table` parameter. Specifically, in: ```go query := fmt.Sprintf("SELECT * FROM %s ORDER BY rowid DESC LIMIT 1", table) ``` Any value passed as the `table` parameter is directly interpolated into the SQL string, enabling injection attacks. This is reachable via API interfaces that expose time-series queries. ### PoC 1. **Deploy eKuiper instance** (default config is sufficient). 2. **Send a crafted request to the SQL query endpoint**: ```bash curl -X POST http://localhost:9081/sql-query \ -H "Content-Type: application/json" \ -d '{ "table": "sensors; DROP TABLE users; --", "operation": "getLast" }' ``` 3. **Effect**: Executes two SQL queries — the first selects data, the second drops the `users` table. 4. **Verify Result**: ```bash sqlite3 etc/kuiper/data/kuiper.db ".tables" ``` ### Impact CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') ### Refferences - https://github.com/lf-edge/ekuiper/commit/72c4918744934deebf04e324ae66933ec089ebd3

Advisory Timeline

  • First published July 24, 2025 (445 days ago).
  • Last revised September 10, 2026 — 413 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update github.com/lf-edge/ekuiper/v2 to 2.2.1 or later
go get github.com/lf-edge/ekuiper/v2@v2.2.1

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

Affects 1 ecosystem: go (2).

PackageEcosystemAffectedFixed In
github.com/lf-edge/ekuiper
go
All versionsRange-based data available
github.com/lf-edge/ekuiper/v2
go
All versions2.2.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.8 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Frequently Asked Questions

What is CVE-2025-54379?
eKuiper API endpoints handling SQL queries with user-controlled table names. This vulnerability has been assigned a severity rating of HIGH (CVSS score: 9.8/10).
How do I check if my project is affected by CVE-2025-54379?
CVE-2025-54379 affects github.com/lf-edge/ekuiper and github.com/lf-edge/ekuiper/v2. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-54379 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.8

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-526j-mv3p-f4vv
GO-2025-3827
PYSEC-2025-241

Related CVEs

  • CVE-2026-107809
    HIGH

    Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

  • CVE-2026-107813
    HIGH

    Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies