CVE-2025-54379

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-22548 (ENISA EUVD) · GHSA-526j-mv3p-f4vv (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 24, 2025

Last Modified

October 10, 2025

Advisory Details (2)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

eKuiper API endpoints handling SQL queries with user-controlled table names. · Advisory · lf-edge/ekuiper · GitHub

https://github.com/lf-edge/ekuiper/security/advisories/GHSA-526j-mv3p-f4vv
GitHub commit

commit 72c491874493 (lf-edge/ekuiper)

Fix landed in lf-edge/ekuiper commit 72c491874493 — awaiting tagged release

https://github.com/lf-edge/ekuiper/commit/72c4918744934deebf04e324ae66933ec089ebd3

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/lf-edge/ekuiper—ghsa
gogithub.com/lf-edge/ekuiper/v2 @ 2.2.1 (fixes < 2.2.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 2 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/lf-edge/ekuiper—
  • every version through 1.14.7: no fix on record
  • every version on: no fix on record
—
github.com/lf-edge/ekuiper/v2—
  • every version up to 2.2.1: fixed in 2.2.1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ekuiper0.0.1.post10035392509 ... 2.1.5 (139 versions)
  • every version through 2.1.5: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 219 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 00:51 UTCEG score recompute
  2. 2026-11-03 00:51 UTCGHSA enrichmentGHSA-526j-mv3p-f4vv · GitHub severity HIGH
  3. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-11-02 02:01 UTCEG score recompute
  5. 2026-11-02 02:01 UTCGHSA enrichmentGHSA-526j-mv3p-f4vv · GitHub severity HIGH
  6. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-11-01 08:04 UTCGHSA enrichmentGHSA-526j-mv3p-f4vv · GitHub severity HIGH
  8. 2026-11-01 03:11 UTCEG score recompute
  9. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-31 04:22 UTCEG score recompute
  11. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-10-30 05:31 UTCEG score recompute
  13. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-10-29 06:41 UTCEG score recompute
  15. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-28 07:50 UTCEG score recompute
  17. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-27 09:01 UTCEG score recompute
  19. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-26 08:57 UTCEG score recompute
  21. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-25 16:18 UTCEG score recompute
  23. 2026-10-25 10:07 UTCEG score recompute
  24. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  25. 2026-10-24 11:15 UTCEG score recompute
Show 71 more
  1. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  2. 2026-10-23 12:23 UTCEG score recompute
  3. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  4. 2026-10-22 13:32 UTCEG score recompute
  5. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  6. 2026-10-21 14:39 UTCEG score recompute
  7. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  8. 2026-10-20 15:21 UTCEG score recompute
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-18 17:07 UTCEG score recompute
  11. 2026-10-18 05:26 UTCEG score recompute
  12. 2026-10-17 18:15 UTCEG score recompute
  13. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  14. 2026-10-16 19:24 UTCEG score recompute
  15. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  16. 2026-10-15 16:59 UTCEG score recompute
  17. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  18. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-14 11:00 UTCEG score recompute
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-10-12 16:57 UTCEG score recompute
  22. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-10-11 20:30 UTCEG score recompute
  24. 2026-10-11 18:42 UTCEG score recompute
  25. 2026-10-11 15:17 UTCEG score recompute
  26. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  28. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  29. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  30. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  31. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  32. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  33. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  34. 2026-10-02 00:41 UTCOSV refresh
  35. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  36. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  37. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  38. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  39. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  40. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  41. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  42. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  43. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  44. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  45. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  46. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  47. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  48. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  49. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  50. 2026-09-12 18:00 UTCOSV refresh
  51. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  52. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  53. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  54. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  55. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  56. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  57. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  58. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  59. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  60. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  61. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  62. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  63. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  64. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  65. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  66. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  67. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  68. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  69. 2026-08-24 23:14 UTCOSV refresh
  70. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  71. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.8% · 52nd percentile

Frequently asked(5)

What is CVE-2025-54379?
CVE-2025-54379 is a critical-severity vulnerability; its CVE record was published on July 24, 2025. 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…
When was the CVE record for CVE-2025-54379 published?
The CVE record for CVE-2025-54379 was published on July 24, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 10, 2025; the record at its source may have been updated since.
Is CVE-2025-54379 actively exploited?
CVE-2025-54379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-54379?
CVE-2025-54379 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-54379?
A fix for CVE-2025-54379 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-54379

Explore →

Is Your Infrastructure Affected by CVE-2025-54379?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.