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

High 8.9 Published Updated

Unauthenticated attackers can execute arbitrary SQL commands via manipulated table names in API requests, leading to database compromise.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-54379?

CVE-2025-54379 is a high-severity SQL injection vulnerability in lf-edge ekuiper, published on 24 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

LF Edge eKuiper is a lightweight IoT data analytics and stream processing engine running on resource-constraint edge devices. In versions before 2.2.1, there is a critical SQL Injection vulnerability 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. This is fixed in version 2.2.1.

Weakness: CWE-89

Which versions are affected by CVE-2025-54379?

7 open source packages ship an affected version, including github.com/lf-edge/ekuiper, github.com/lf-edge/ekuiper/v2 and ekuiper. It affects 1 product.

PackageAffectedFixed in
github.com/lf-edge/ekuiper GoAll versionsNone
github.com/lf-edge/ekuiper GoAll versions to 1.14.7None
github.com/lf-edge/ekuiper GoAll versions to 1.14.7None
github.com/lf-edge/ekuiper/v2 GoAll versions2.2.1
github.com/lf-edge/ekuiper/v2 GoAll versions2.2.1
github.com/lf-edge/ekuiper/v2 GoAll versions2.2.1
1 more packages
ekuiper PyPIAll versions to 2.1.5None

Products include Lfedge Ekuiper.

How do I fix CVE-2025-54379?

Upgrade to a fixed version.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2025-54379 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54379 exists.

Sources

Also known as GHSA-526j-mv3p-f4vv, GO-2025-3827, PYSEC-2025-241.

Is CVE-2025-54379 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free