How severe is GHSA-526j-mv3p-f4vv?

No CVSS score has been assigned to GHSA-526j-mv3p-f4vv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-526j-mv3p-f4vv?

GHSA-526j-mv3p-f4vv affects the following packages: github.com/lf-edge/ekuiper/v2 (Go), github.com/lf-edge/ekuiper (Go). Ecosystems affected: Go.

How do I fix GHSA-526j-mv3p-f4vv?

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 GHSA-526j-mv3p-f4vv is resolved across your whole dependency graph.

How do I detect GHSA-526j-mv3p-f4vv 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-526j-mv3p-f4vv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-526j-mv3p-f4vv?

O3 pinpoints whether GHSA-526j-mv3p-f4vv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-526j-mv3p-f4vv actively exploited in the wild?

No public exploit code has been indexed for GHSA-526j-mv3p-f4vv 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 GHSA-526j-mv3p-f4vv?

GHSA-526j-mv3p-f4vv has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 50th 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 GHSA-526j-mv3p-f4vv?

GHSA-526j-mv3p-f4vv 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 GHSA-526j-mv3p-f4vv published, and has it been updated?

GHSA-526j-mv3p-f4vv was published on July 24, 2025 and was last updated on July 29, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-526j-mv3p-f4vv

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

Also known asCVE-2025-54379GO-2025-3827

Published

Jul 24, 2025

Updated

Jul 29, 2025

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk50th percentile+0.40%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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	`github.com/lf-edge/ekuiper`	all versions	No fix

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-526j-mv3p-f4vv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-526j-mv3p-f4vv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-526j-mv3p-f4vv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

O3 Security · Impact-Aware SCA

Is GHSA-526j-mv3p-f4vv in your dependencies?

O3 detects GHSA-526j-mv3p-f4vv across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works