CVE-2025-54947: Apache StreamPark: Use hard-coded key vulnerability

Published Dec 12, 2025
·
Updated

In Apache StreamPark versions 2.0.0 through 2.1.7, a security vulnerability involving a hard-coded encryption key exists. This vulnerability occurs because the system uses a fixed, immutable key for encryption instead of dynamically generating or securely configuring the key. Attackers may obtain this key through reverse engineering or code analysis, potentially decrypting sensitive data or forging encrypted information, leading to information disclosure or unauthorized system access.

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.

Affected Software

3 affected componentsFixes available
Apache StreamPark>=2.0.0<2.1.7
maven/org.apache.streampark:streampark>=2.0.0<2.1.7
2.1.7
Apache StreamPark>=2.0.0<2.1.7

Event History

Dec 12, 2025
CVE Published
via MITRE·03:11 PM
Data Sourced
via MITRE·03:11 PM
DescriptionWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·03:30 PM
Data Sourced
via GitHub·03:30 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-54947?

The severity of CVE-2025-54947 is classified as high due to the use of a hard-coded encryption key.

2

How do I fix CVE-2025-54947?

To fix CVE-2025-54947, upgrade Apache StreamPark to a version later than 2.1.7 where this vulnerability is addressed.

3

What versions of Apache StreamPark are affected by CVE-2025-54947?

Apache StreamPark versions 2.0.0 through 2.1.7 are affected by CVE-2025-54947.

4

What impact does CVE-2025-54947 have on security?

CVE-2025-54947 can lead to unauthorized data access if the hard-coded key is exposed to attackers.

5

Is there a workaround for CVE-2025-54947 before upgrading?

There are no effective workarounds for CVE-2025-54947, and upgrading is the recommended action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203