How severe is CVE-2025-54379?

No CVSS score has been assigned to CVE-2025-54379 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-54379?

CVE-2025-54379 affects the following packages: github.com/lf-edge/ekuiper/v2 (Go), github.com/lf-edge/ekuiper (Go). Ecosystems affected: Go.

How do I fix CVE-2025-54379?

Update github.com/lf-edge/ekuiper/v2 to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54379 is resolved across your whole dependency graph.

How do I detect CVE-2025-54379 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/ekuiper/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-54379 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2025-54379 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-54379 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-54379?

CVE-2025-54379 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-54379?

CVE-2025-54379 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-54379 published, and has it been updated?

CVE-2025-54379 was published on July 24, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-54379 — ekuiper

Fix: lf-edge/ekuiper@72c4918

CVE-2025-54379 is a SQL Injection vulnerability in github.com/lf-edge/ekuiper/v2. A fix is available for github.com/lf-edge/ekuiper/v2 — see the affected versions and patch details below.

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

Also known asGHSA-526j-mv3p-f4vvGO-2025-3827PYSEC-2025-241

Published

Jul 24, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-54379.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/lf-edge/ekuiper/v2🐹github.com/lf-edge/ekuiper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

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

Deploy eKuiper instance (default config is sufficient).
Send a crafted request to the SQL query endpoint:

   curl -X POST http://localhost:9081/sql-query \
     -H "Content-Type: application/json" \
     -d '{
       "table": "sensors; DROP TABLE users; --",
       "operation": "getLast"
     }'

Effect: Executes two SQL queries — the first selects data, the second drops the users table.
Verify Result:

   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

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/lf-edge/ekuiper/v2`	all versions	2.2.1`go get github.com/lf-edge/ekuiper/v2@v2.2.1`
🐹Go	`github.com/lf-edge/ekuiper`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

ekuiperlfedge

1 version

2.1.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/ekuiper/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/lf-edge/ekuiper/v2 to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54379 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### 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.Sp