dbcve.org
StreamparkApplication · Apache

CVE-2025-53960

MEDIUM · 5.9 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 2.1.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache StreamPark incorrectly uses the user's password as the HMAC signing key (HS256) when generating JWTs. This allows an attacker with a captured token to perform offline brute-force attacks on the password, or if the password is known, forge arbitrary tokens for complete account takeover.

MitigationUpgrade to Apache StreamPark version 2.1.7 which implements proper secret-based JWT signing separate from user credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StreamparkApplication
Affected:>= 2.0.0, < 2.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache StreamPark version
    Check the installed StreamPark version by examining the pom.xml, build artifacts, or the application's runtime startup banner. Common locations: $STREAMPARK_HOME/streampark-common/target or check the Docker image tag if using containers.
    Affected if Version is >= 2.0.0 and < 2.1.7
  2. Confirm JWT authentication is in use
    Inspect application logs during login or examine the authentication configuration files (typically in conf/ or resources/ directories) to determine if JWT-based authentication is enabled for user sessions.
    Affected if JWT authentication is enabled and users can log in to the application
  3. Capture and inspect a JWT token
    Log into the StreamPark application and retrieve a JWT token from browser developer tools (Application/Storage tab) or API responses. Decode the token header to verify the algorithm is HS256.
    Affected if The token uses HS256 algorithm and the application is in the affected version range
  4. Review token signing implementation
    Examine the StreamPark source code or decompiled classes related to JWT generation (look for JwtTokenUtil, JwtHelper, or similar classes) to verify the signing key is derived from user credentials rather than a dedicated secret.
    Affected if The code uses user password or password-derived value as the signing key instead of a separate secret

You are affected if Apache StreamPark version is between 2.0.0 and 2.1.6 (inclusive) and JWT authentication is enabled, with tokens signed using the user's password as the HMAC key.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.7 or later
Fixed in 2.1.7
Interim mitigation

Upgrade to Apache StreamPark version 2.1.7 which implements proper secret-based JWT signing separate from user credentials.

Recommended fix High confidence

2.1.7

  1. 1. Back up your current Apache StreamPark installation and database
  2. 2. Download Apache StreamPark version 2.1.7 from the official Apache repository (https://streampark.apache.org/download/)
  3. 3. Stop the running StreamPark service
  4. 4. Upgrade to version 2.1.7 following the official upgrade documentation
  5. 5. Verify that JWT tokens are now signed with a proper cryptographic key rather than the user's password
  6. 6. Restart the StreamPark service
  7. 7. Confirm that user authentication and authorization work correctly after the upgrade
Caveat Review release notes for any breaking changes between your current version and 2.1.7

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Streampark Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53960 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data