CVE-2025-54947VulnerabilityPublished 12 Dec 2025

CVE-2025-54947: Apache StreamPark · Use of Hard-coded Cryptographic Key

Affects Apache StreamParkSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.1.7 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.1.7

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.apache.streampark/streampark to 2.1.7.

Affected software

Product	Affected	Fixed in
Mavenorg.apache.streampark/streampark`pkg:maven/org.apache.streampark/streampark`Other threats	Affected =2.0.0 >=2.0.0 <2.1.7	Fixed in 2.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all Apache StreamPark deployments to version 2.1.7 or later, which eliminates the hard-coded key vulnerability. 2. Conduct a thorough audit of cryptographic key management practices within the organization to ensure no other components use hard-coded or weak keys. 3. Review and rotate any encryption keys or credentials that may have been exposed due to this vulnerability. 4. Implement network monitoring and anomaly detection focused on encrypted data flows and authentication tokens to detect potential misuse or unauthorized decryption attempts. 5. Restrict access to Apache StreamPark binaries and source code repositories to minimize risk of key extraction via insider threats. 6. Educate development and security teams on secure cryptographic practices to prevent recurrence of similar issues. 7. For critical environments, consider additional encryption layers or hardware security modules (HSMs) to safeguard keys. 8. Maintain an inventory of all systems running affected versions to ensure comprehensive patching and risk management.

Description

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.

Impact

For European organizations, the primary impact of CVE-2025-54947 is the potential exposure of sensitive data encrypted by Apache StreamPark, which could include operational data, configuration secrets, or user information. This confidentiality breach could lead to secondary attacks such as unauthorized access or data manipulation if attackers leverage decrypted information. Organizations in sectors relying on Apache StreamPark for data processing or streaming analytics—such as finance, telecommunications, manufacturing, and critical infrastructure—may face increased risk. The vulnerability could undermine trust in data confidentiality and compliance with data protection regulations like GDPR, potentially resulting in legal and reputational consequences. Since the vulnerability does not affect integrity or availability, operational disruptions are less likely, but the risk of data leakage remains significant. European entities using outdated versions should prioritize patching to prevent exploitation, especially given the ease of key extraction and remote exploitation without authentication.

CWE-321Use of Hard-coded Cryptographic Key (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a hard-coded, unchangeable cryptographic key.
Architecture and Design
Prevention schemes mirror that of hard-coded password storage.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 16:28 UTC

WeaknessesCWE-321

Technical details

References

Community reviews

Related threats