# CVE-2025-53960: Apache StreamPark: Uses the user’s password as the secret key

> Apache StreamPark uses user passwords as JWT signing keys, allowing attackers to brute-force passwords or forge tokens for account takeover.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 16 Dec 2025
- **Also known as:** GHSA-3hg2-rh4r-8qf6

## What is CVE-2025-53960?

CVE-2025-53960 is a medium-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

When issuing JSON Web Tokens (JWT), Apache StreamPark directly uses the user's password as the HMAC signing key (e.g., with the HS256 algorithm). An attacker can exploit this vulnerability to perform offline brute-force attacks on the user's password using a captured JWT, or to arbitrarily forge identity tokens for the user if the password is already known, ultimately leading to complete account takeover.

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-1240 (Use of a Cryptographic Primitive with a Risky Implementation)

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

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-53960?

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

## Is CVE-2025-53960 being exploited?

There is no known exploitation of CVE-2025-53960 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-53960 and fix it if it is affected.

What it is: CVE-2025-53960 is a medium-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-53960 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-53960/ (Markdown: https://insights.sbomify.com/CVE-2025-53960/index.md)
```

## Sources

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

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