# CVE-2025-54981: Apache StreamPark: Weak Encryption Algorithm in StreamPark

> Weak encryption in Apache StreamPark allows attackers to potentially decrypt sensitive JWT tokens and authentication data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2025
- **Updated:** 12 Dec 2025
- **Also known as:** GHSA-749j-2hp6-8cxm

## What is CVE-2025-54981?

CVE-2025-54981 is a high-severity vulnerability in Apache StreamPark, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Weak Encryption Algorithm in StreamPark, The use of an AES cipher in ECB mode and a weak random number generator for encrypting sensitive data, including JWT tokens, may have risked exposing sensitive authentication data

This issue affects Apache StreamPark: from 2.0.0 before 2.1.7.

Users are recommended to upgrade to version 2.1.7, which fixes the issue.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2025-54981?

2 open source packages ship an affected version, including org.apache.streampark:streampark. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.streampark:streampark` | Maven | From 2.0.0 | 2.1.7 |
| `org.apache.streampark:streampark` | Maven | From 2.0.0 | 2.1.7 |

Products: Apache Streampark.

## How do I fix CVE-2025-54981?

Upgrade org.apache.streampark:streampark to 2.1.7 or later.

## Is CVE-2025-54981 being exploited?

There is no known exploitation of CVE-2025-54981 in the wild and no public exploit code.

## Other vulnerabilities in Apache StreamPark

- [CVE-2022-45802](https://insights.sbomify.com/CVE-2022-45802/): Apache StreamPark (incubating): Upload any file to any directory (critical 9.8)
- [CVE-2024-29070](https://insights.sbomify.com/CVE-2024-29070/): Apache StreamPark: session not invalidated after logout (critical 9.1)
- [CVE-2022-46365](https://insights.sbomify.com/CVE-2022-46365/): Apache StreamPark (incubating): Logic error causing any account reset (critical 9.1)
- [CVE-2024-29178](https://insights.sbomify.com/CVE-2024-29178/): Apache StreamPark: FreeMarker SSTI RCE Vulnerability (high 8.8)
- [CVE-2023-52291](https://insights.sbomify.com/CVE-2023-52291/): Apache StreamPark (incubating): Unchecked maven build params could trigger remote command execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54981 and fix it if it is affected.

What it is: CVE-2025-54981 is a high-severity vulnerability in Apache StreamPark, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54981 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.streampark:streampark (Maven): affected from 2.0.0; fixed in 2.1.7
- org.apache.streampark:streampark (Maven): affected from 2.0.0; fixed in 2.1.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54981/ (Markdown: https://insights.sbomify.com/CVE-2025-54981/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54981
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54981
- OSV: https://osv.dev/vulnerability/CVE-2025-54981

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54981/
Summaries are generated and may contain mistakes; the official description above is the record.