VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.streampark:streampark: vulnerability history, versions and safety

org.apache.streampark:streampark is a package in the Maven ecosystem. Vulert records 12 vulnerabilities for it across 3 releases, from May 2023 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded C2 H5 M5
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 12 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.streampark:streampark vulnerabilities

Vulert verdict on org.apache.streampark:streampark 2.1.5 i

Updated on 23 Oct 2026

Careful: 2.1.5 has 4 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.1.5 — affected i
  • Vulnerabilities on record 12 over 2 years · 3 in the last year i
  • Latest disclosure 12 Dec 2025 i
  • Highest CVSS 9.1 i
  • With no published fix 1 i
  • Stars 4,344 i
  • Last release 24 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.streampark:streampark, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.1.5 09 Oct 2024 H4 Apache-2.0 No Details →
2.1.0 02 May 2023 C1 H5 M4 Apache-2.0 No Details →
2.0.0 14 Feb 2023 C1 H5 M4 Apache-2.0 No Details →

All 3 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 4
  • 2024 4
  • 2025 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 12 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.streampark:streampark

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-46365: Apache StreamPark Improper Input Validation vulnerability 9.1 critical 2.0.0 06 Jul 2023
CVE-2024-29178: Apache StreamPark FreeMarker SSTI RCE Vulnerability 8.8 high 2.1.4 18 Jul 2024
CVE-2025-54981: Apache StreamPark Weak Encryption Algorithm Vulnerability 8.7 high 2.1.7 12 Dec 2025
CVE-2025-53960: Apache StreamPark Weak Encryption Key Vulnerability 8.7 high 2.1.7 12 Dec 2025
CVE-2025-54947: Apache StreamPark Hard-Coded Encryption Key Vulnerability 8.7 high 2.1.7 12 Dec 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.streampark:streampark

Is org.apache.streampark:streampark safe to use?

Vulert records 12 vulnerabilities for org.apache.streampark:streampark in Maven: 2 critical, 5 high, 5 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.apache.streampark:streampark's Vulert package health score?

Vulert scores org.apache.streampark:streampark 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.apache.streampark:streampark affected?

Yes. 2.1.5, the version you would install today, has 4 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.apache.streampark:streampark should I use?

2.1.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.streampark:streampark have?

12 vulnerabilities are recorded for org.apache.streampark:streampark in the Maven ecosystem: 2 critical, 5 high, 5 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.streampark:streampark vulnerabilities disclosed?

3 vulnerabilities were recorded for org.apache.streampark:streampark in the last 12 months, and the oldest entry in this database dates to 01 May 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.streampark:streampark are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.streampark:streampark for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.streampark:streampark version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.