cve.bz

CVE-2025-54947 apache streampark: Use of Hard-coded Credentials

9.8 criticalEPSS 0.5%Fix available

Critical (9.8) in apache streampark. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.streampark:streampark 2.1.7.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-12-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-798 Use of Hard-coded Credentials
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • org.apache.streampark:streampark (Maven): fixed in 2.1.7

Ask an AI about this CVE

Show the promptExplain CVE-2025-54947 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-54947?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-54947?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-54947 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-54947

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-54947](https://cve.bz/cve/badge/CVE-2025-54947.svg)](https://cve.bz/cve/CVE-2025-54947)

HTML:

<a href="https://cve.bz/cve/CVE-2025-54947"><img src="https://cve.bz/cve/badge/CVE-2025-54947.svg" alt="CVE-2025-54947"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache StreamParkfrom 2.0.0 before 2.1.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-prv5-c2px-j9q3Mavenorg.apache.streampark:streampark>=2.0.0 <2.1.72.1.7

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON