CVE-2025-54379

CVE-2025-54379 is a high-severity SQL injection vulnerability in github.com/lf-edge/ekuiper/v2 (go), affecting versions < 2.2.1. It is fixed in 2.2.1.

Summary

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

Impact

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Affected versions

github.com/lf-edge/ekuiper/v2 (< 2.2.1) github.com/lf-edge/ekuiper (<= 1.14.7)

Security releases

github.com/lf-edge/ekuiper/v2 → 2.2.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade github.com/lf-edge/ekuiper/v2 to 2.2.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-54379? CVE-2025-54379 is a high-severity SQL injection vulnerability in github.com/lf-edge/ekuiper/v2 (go), affecting versions < 2.2.1. It is fixed in 2.2.1. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
  2. Which packages are affected by CVE-2025-54379?
    • github.com/lf-edge/ekuiper/v2 (go) (versions < 2.2.1)
    • github.com/lf-edge/ekuiper (go) (versions <= 1.14.7)
  3. Is there a fix for CVE-2025-54379? Yes. CVE-2025-54379 is fixed in 2.2.1. Upgrade to this version or later.
  4. Is CVE-2025-54379 exploitable, and should I be worried? Whether CVE-2025-54379 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2025-54379 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2025-54379? Upgrade github.com/lf-edge/ekuiper/v2 to 2.2.1 or later.

Other vulnerabilities in github.com/lf-edge/ekuiper/v2

CVE-2025-54379CVE-2024-52290

Stop the waste.
Protect your environment with Kodem.