Skip to main content
VulnerabilityPublished

CVE-2025-54379: lf-edge ekuiper · SQL Injection

Affects lf-edge ekuiperSource CVE Database V5

0

Public exploit available · CVSS 8.9 High : upgrade to 2.2.1 as a priority.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade lf-edge/ekuiper to 2.2.1.

Affected software

ProductAffectedFixed in
GitHublf-edge/ekuiperpkg:github/lf-edge/ekuiperOther threatsAffected
  • <2.2.1
Fixed in
  • 2.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately assess their deployments of eKuiper and identify any instances running versions prior to 2.2.1. The primary mitigation is to upgrade all affected eKuiper instances to version 2.2.1 or later, where the vulnerability is patched. In addition, organizations should implement network-level controls to restrict access to the eKuiper API endpoints, limiting exposure to trusted networks or VPNs. Employing Web Application Firewalls (WAFs) with SQL injection detection rules can provide an additional layer of defense. Monitoring and logging API requests for unusual patterns or unexpected table name parameters can help detect attempted exploitation. For environments where immediate patching is not feasible, consider isolating vulnerable devices from untrusted networks and applying strict ingress filtering. Finally, organizations should review and harden IoT device security policies, including regular vulnerability scanning and incident response readiness specific to edge computing components.

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.

References

Community reviews

Loading reviews…