CVE-2025-30001VulnerabilityPublished 10 Oct 2025Updated 5 Nov 2025

Org.apache.streampark:streampark: Apache StreamPark contains an Incorrect Execution-Assigned Permissions vulnerability

Affects org.apache.streampark:streamparkSource GCVE Database

Compare

Authoritative record:CVE-2025-30001· High 7.3

Not known to be exploited · CVSS 7.3 High · fixed in 2.1.6 : patch org.apache.streampark:streampark soon.

Data as of 4 Nov 2026, 18:18 UTC

CVSS 3.1 base score

7.3High

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

Patch: Available – fixed in 2.1.6

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

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

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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 4 Nov 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
Mavenorg.apache.streampark:streampark	Affected <=2.1.5	Fixed in–

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

AI-suggested

Users should upgrade to Apache StreamPark version 2.1.6 once it is published in the Maven registry, as this version contains the fix for the vulnerability. Until the fixed version is available, users should consider restricting access to affected versions and monitor for the official release.

Description

Apache StreamPark versions from 2.1.4 up to 2.1.5 contain an Incorrect Execution-Assigned Permissions vulnerability. This flaw allows unauthorized permission assignments during execution, potentially leading to confidentiality, integrity, and availability impacts. The issue is fixed in version 2.1.6, which is not yet published in the Maven registry.

Impact

The vulnerability allows incorrect permission assignments during execution, which can lead to unauthorized access or modification of resources, impacting confidentiality, integrity, and availability of the affected system. The CVSS score of 7.3 reflects a high severity with network exploitability and no required privileges or user interaction.

Summary

CVE-2025-30001 describes an Incorrect Execution-Assigned Permissions vulnerability in Apache StreamPark affecting versions from 2.1.4 before 2.1.6. The vulnerability is classified under CWE-279 and has a CVSS v3.1 base score of 7.3 (high severity), indicating network attack vector, low attack complexity, no privileges required, and no user interaction needed. Successful exploitation could lead to partial loss of confidentiality, integrity, and availability. The vendor recommends upgrading to version 2.1.6 to remediate the issue; however, this version is not yet available in the Maven registry.

CWE-279Incorrect Execution-Assigned Permissions (opens in a new tab)
Variant weakness
While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Web Server Logs Tampering (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 4 Nov 2026, 18:18 UTC

WeaknessesCWE-279

Technical details

References

Community reviews

Related threats