dbcve.org
StreamparkApplication · Apache

CVE-2025-30001

HIGH · 7.3 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 2.1.6 or later.
See remediation →
82/100
Remediation priority · High
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
Incorrect Execution-Assigned Permissions vulnerability in Apache StreamPark. This issue affects Apache StreamPark: from 2.1.4 before 2.1.6. Users are recommended to upgrade to version 2.1.6, 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 · moderate confidence

Apache StreamPark versions 2.1.4 through before 2.1.6 contain an Incorrect Execution-Assigned Permissions vulnerability, allowing unauthorized access or actions due to improper permission handling during execution. The specific nature of the permission misconfiguration is not detailed, but the HIGH severity (7.3 CVSS) indicates significant potential for abuse.

MitigationUpgrade Apache StreamPark to version 2.1.6 or later to resolve the permission handling vulnerability.

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.1.4, < 2.1.6

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 StreamPark installation method
    Determine how StreamPark was installed: check for /opt/streampark, /usr/local/streampark, or the installation directory. Also check for Docker containers with 'streampark' in the name using 'docker ps -a'.
    Affected if StreamPark is installed on the system
  2. Locate the installed version
    For source builds, check the pom.xml or version.properties in the StreamPark installation directory. For binary installations, check for a VERSION file or run 'streampark --version' if available. For Docker, inspect the image tag using 'docker images | grep streampark'.
    Affected if The version cannot be determined or the file is missing
  3. Compare version against affected range
    If the version is found, parse it and compare: versions 2.1.4, 2.1.5, or any version >= 2.1.4 and < 2.1.6 are affected. Version 2.1.6 and later are not affected.
    Affected if Installed version is 2.1.4, 2.1.5, or falls between 2.1.4 and 2.1.6 (e.g., 2.1.4.1, 2.1.5.2)
  4. Verify current running version
    If StreamPark is running, access the web UI and check the About or Settings page for the version number. Alternatively, check running process or service status: 'systemctl status streampark' or 'ps aux | grep streampark'.
    Affected if Running version differs from installed version and the running version is affected

A system is affected by CVE-2025-30001 if Apache StreamPark version 2.1.4, 2.1.5, or any version >= 2.1.4 and < 2.1.6 is installed or running.

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.6 or later
Fixed in 2.1.6
Interim mitigation

Upgrade Apache StreamPark to version 2.1.6 or later to resolve the permission handling vulnerability.

Recommended fix High confidence

2.1.6

  1. Back up your current Apache StreamPark installation and configuration
  2. Download Apache StreamPark version 2.1.6 from the official Apache source
  3. Upgrade your existing StreamPark installation to version 2.1.6
  4. Verify the upgrade was successful by checking the version number in the UI or via command line
  5. Test that all functionality works as expected post-upgrade

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

Fix this in Streampark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30001 — 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-30001 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