Loading vulnerability…
Apache StreamPark contains a hard-coded (fixed/immutable) encryption key in versions 2.0.0 through 2.1.7. Because the key is embedded and not dynamically generated or securely configured, an attacker who can obtain the application code (e.g., via reverse engineering or source/code analysis) may recover the key and use it to decrypt data protected by this mechanism or to forge encrypted values, undermining confidentiality and trust in encrypted artifacts. The issue is tracked as CVE-2025-54947 and is reported as fixed in StreamPark 2.1.7.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Apache StreamPark. No further details provided in the content.
A critical hard-coded encryption key vulnerability in Apache StreamPark (CVE-2025-54947) allows attackers to decrypt sensitive data and gain unauthorized access to affected systems. The flaw impacts versions 2.0.0 through 2.1.7 and is resolved in version 2.1.7.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.