Skip to main content
VulnerabilityPublished Updated

CVE-2024-48988: Apache StreamPark · SQL Injection Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2024-48988· High 7.6

Not known to be exploited · CVSS 7.6 High · fixed in 2.1.6 : patch Apache StreamPark soon.

Data as of 4 Nov 2026, 17:57 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.6
Patch
Available – fixed in 2.1.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.streampark/streamparkpkg:maven/org.apache.streampark/streamparkOther threatsAffected
  • =2.1.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache StreamPark to version 2.1.6 or later to remediate this vulnerability. Since the issue only affects the SpringBoot distribution package, users relying on Maven artifacts are not impacted. No additional mitigation steps are indicated.

Description

An SQL Injection vulnerability exists in Apache StreamPark versions from 2.1.4 up to but not including 2.1.6. This flaw is present only in the SpringBoot distribution package and requires a user to be authenticated before exploitation, reducing the overall risk. The issue is fixed in version 2.1.6.

References

Community reviews

Loading reviews…