CVE-2025-54379: GO-2025-3827 - eKuiper API endpoints handling SQL queries with user-controlled table names. in github.com/lf-edge/ekuiper

CVE-2025-54379 · Severity: medium · CVSS 4 · Published 2025-07-29

eKuiper API endpoints handling SQL queries with user-controlled table names. in github.com/lf-edge/ekuiper

Technologies: github.com/lf-edge/ekuiper (Go), github.com/lf-edge/ekuiper/v2 (Go). Vendors: Go, PyPI.

Quick answers

Is CVE-2025-54379 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-54379 being exploited in the wild.
How severe is CVE-2025-54379?
Medium severity, with a CVSS score of 4, published 29 July 2025.
Which products and versions are affected?
github.com/lf-edge/ekuiper (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.14.7; github.com/lf-edge/ekuiper/v2 (Go) SEMVER:introduced=0,fixed=2.2.1; ekuiper (PyPI) ECOSYSTEM:introduced=0,last_affected=2.1.5.
Is there a fix for CVE-2025-54379?
Yes. github.com/lf-edge/ekuiper/v2 (Go): upgrade to 2.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-54379?
Check whether you run github.com/lf-edge/ekuiper (Go), github.com/lf-edge/ekuiper/v2 (Go) or ekuiper (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/lf-edge/ekuiper/v2 (Go): upgrade to 2.2.1 or later
    go get github.com/lf-edge/ekuiper/v2@v2.2.1

Affected products

  • github.com/lf-edge/ekuiper (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.14.7
  • github.com/lf-edge/ekuiper/v2 (Go) SEMVER:introduced=0,fixed=2.2.1
  • ekuiper (PyPI) ECOSYSTEM:introduced=0,last_affected=2.1.5

Identifiers

  • CVE-2025-54379
  • GHSA-526j-mv3p-f4vv
  • GO-2025-3827
  • PYSEC-2025-241

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.