Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5amended

LF Edge eKuiper: SSRF in External Service

CVE-2025-24979GHSA-pqqc-8v73-9gg2

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/lf-edge/ekuiper/v2

    Affected
    < 2.4.0
    Fixed in
    2.4.0

  • Go github.com/lf-edge/ekuiper

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary Server-side request forgery (SSRF) vulnerability in eKuiper allows an attacker with permissions to register external services or create rules to induce the eKuiper server to make requests to unintended network locations, such as internal services, loopback interfaces (localhost), or cloud metadata endpoints. Details Prior to v2.4.0, eKuiper external service registrations and HTTP invocations did not validate destination IP addresses. An attacker with access to the eKuiper management API could register an external service pointing to an internal address (such as http://127.0.0.1:9081 or other internal network services) and trigger queries using service functions (e.g. SELECT tsschemaless(...) FROM demo). This allows probing internal networks, leaking sensitive information (such as internal endpoints/credentials), or interacting with internal APIs accessible to the eKuiper host. PoC 1. Create an external service with an address pointing to an internal network / localhost: 2.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-pqqc-8v73-9gg2

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6447

  3. Revision 1 · created ·

    Published from osv record GHSA-pqqc-8v73-9gg2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-24979

Advisory: LF Edge eKuiper: SSRF in External Service
IDs: CVE-2025-24979, GHSA-pqqc-8v73-9gg2
Record: https://patchnext.com/advisories/cve-2025-24979 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/lf-edge/ekuiper/v2 2.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lf-edge/ekuiper/v2: affected < 2.4.0; fixed in 2.4.0
- Go github.com/lf-edge/ekuiper: affected every version

## Suggested inspection (read-only)
- Go github.com/lf-edge/ekuiper/v2: check the installed version with your package manager.
- Go github.com/lf-edge/ekuiper: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lf-edge/ekuiper/v2, github.com/lf-edge/ekuiper.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pqqc-8v73-9gg2 (OSV record GHSA-pqqc-8v73-9gg2 lists affected ranges: Go github.com/lf-edge/ekuiper/v2 >=0 <2.4.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6447 (OSV record GO-2026-6447 lists affected ranges: Go github.com/lf-edge/ekuiper >=0; Go github.com/lf-edge/ekuiper/v2 >=0 <2.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-pqqc-8v73-9gg2 (GitHub-reviewed advisory GHSA-pqqc-8v73-9gg2 lists affected ranges: Go github.com/lf-edge/ekuiper/v2 >=0 <2.4.0)

Commands are suggestions: review each one before running it.

Loading voting…