Skip to main content

Apache StreamPark CVE-2025-30001

HIGH
Incorrect Execution-Assigned Permissions (CWE-279)
2025-10-10 security@apache.org
7.3
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed StreamPark instance
  2. Exploit
    Submit or trigger affected task
  3. Execution
    Task runs with incorrect permissions
  4. Impact
    Access or alter unauthorized data

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V8 - Authorization Incorrect execution permissions
Exploitation Conditions

The advisory provides no concrete prerequisites beyond the affected version range (Apache StreamPark 2.1.4 through 2.1.5; fixed in 2.1.6), so the exact feature or configuration triggering the incorrect permission assignment is not disclosed. The weakness class (CWE-279) implies the attacker needs to reach a code path where StreamPark executes a task or process with mis-assigned permissions - typically meaning the StreamPark web/API service must be network-reachable and the affected execution feature in use. Limiting factors: the real-world impact is partial (C:L/I:L/A:L), and despite the NVD PR:N rating, permission-assignment flaws of this type commonly require an existing low-privileged account, so defenders should treat unauthenticated exploitability as unconfirmed pending vendor detail.

Impact

This is a moderate-severity issue (CVSS 7.3) that does not rise to an emergency priority. The NVD CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw, which on paper is concerning, but the impact is only Low across confidentiality, integrity, and availability (C:L/I:L/A:L), consistent with a partial permissions weakness rather than full system compromise. The EPSS score is low (0.55%, 45th percentile), indicating no meaningful signal of imminent mass exploitation. There is no CISA KEV listing and no public exploit code identified, so exploitation status is speculative. One point of friction: the underlying weakness is CWE-279 (Incorrect Execution-Assigned Permissions), which typically describes a process or task running with more permissions than intended - this usually presumes some existing access or an authenticated foothold, yet the NVD vector asserts PR:N (unauthenticated). This PR:N rating should be verified with the Apache advisory, as a pure 'execution-assigned permissions' flaw more commonly requires a low-privileged user. No SSVC decision data was provided. Overall: a real but non-critical issue - patch on a normal cadence, not as a fire drill.

Exploit ScenarioDerived

A remote attacker interacts with an exposed Apache StreamPark instance (versions 2.1.4-2.1.5) where a task or process is executed with incorrectly assigned permissions, allowing the attacker to read or modify data or affect availability beyond their intended privilege level. Because CVSS rates attack complexity as low and the impact as partial across C/I/A, the practical outcome is limited information disclosure or minor tampering rather than full takeover. No public proof-of-concept exploit has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Incorrect permission assignment in Apache StreamPark 2.1.4 and 2.1.5 causes tasks launched by the platform to execute under the wrong privilege context, giving a remote attacker who can reach the affected code path limited but real confidentiality, integrity, and availability impact. NVD rates the issue 7.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L), while our independent assessment scores the same vector with PR:L, treating unauthenticated exploitability as unconfirmed pending vendor detail; the described impact is partial on all three metrics. There is no indication of active exploitation - the CVE is not in CISA KEV and no public exploit code has been identified at time of analysis - and EPSS is low at 0.55% (45th percentile). Authentication requirements are not confirmed from available data. Vendor-released patch: 2.1.6.

RemediationAI

Apply the vendor fix by upgrading Apache StreamPark to version 2.1.6 or later, as stated in the Apache advisory at https://lists.apache.org/thread/xfmsvhkcnr1831n0w5ovy3p44lsmfb7m - this is the only complete remediation, since the specific mis-assigned permission path is not publicly detailed and cannot be individually reconfigured with confidence. Until the upgrade is complete, reduce exposure with targeted compensating controls: restrict network access to the StreamPark web/API endpoints to trusted management networks or a reverse-proxy allowlist, which removes the remote attack surface but complicates legitimate remote administration; enforce authentication and avoid shared or administrator-level StreamPark accounts, which limits an attacker's starting privilege but does not close the flaw for any authenticated user; run the StreamPark service (and any container running it) under a dedicated unprivileged OS user with no elevated group membership or host filesystem mounts, so a mis-assigned task execution cannot inherit high privilege - side effects include job or cluster operations that require broader rights failing until permissions are granted explicitly; and audit existing StreamPark-launched processes, generated files, and job artifacts for unexpected ownership or world-readable/writable modes, remediating anything created while a vulnerable version was deployed. Enable verbose task-execution logging to detect unexpected privilege context, and note that blocking or disabling task-submission features is the most restrictive fallback and will break StreamPark's core functionality. Because no public exploit code has been identified at time of analysis, patch scheduling can follow normal moderate-severity cycles rather than emergency change procedures.

Affected Packages

maven org.apache.streampark:streampark no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in maven

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache StreamPark is a stream-processing development and management platform, commonly used to build, submit, and operate Apache Flink jobs and related pipelines, so it routinely spawns processes and tasks on behalf of users. The root cause class is CWE-279, Incorrect Execution-Assigned Permissions, a permission-management weakness in which the software runs code or a process with a privilege level that does not match the intended security policy - often because ownership, user/group, or mode is set from untrusted or misapplied input, rather than from a memory-safety defect. In practice this means a task or process started through StreamPark may run with broader rights than the invoking user should receive (for example, as the StreamPark service account or another privileged principal), or that a resource is created with overly permissive ownership/mode. Because exploitation depends on reaching the specific execution path where the assignment occurs, the platform's web/API surface must be network-reachable and the affected task-execution feature must be in use; the advisory discloses no further prerequisites, and the CPE entry cpe:2.3:a:apache:streampark:*:*:*:*:*:*:*:* is not version-bounded, so the authoritative affected range is the advisory's 'from 2.1.4 before 2.1.6'. The PR:N versus PR:L discrepancy between NVD and our assessment reflects the fact that permission-assignment flaws of this type frequently require an existing low-privileged account, so the practical attack surface should be treated as unconfirmed.

Know when Streampark gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 7.3 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
vuln.today AI 6.3 MEDIUM

Network-reachable, low-complexity service; PR:L chosen because an execution-assigned-permissions flaw (CWE-279) typically presumes a low-privileged foothold, with partial C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

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

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Apache StreamPark versions 2.1.4 and 2.1.5 can launch platform-managed jobs under an incorrect privilege context, allowing anyone who can reach the affected code path to operate with rights that should not be theirs - a limited but genuine exposure of confidentiality, integrity, and availability. Because StreamPark typically orchestrates an organization's real-time data pipelines, an issue at this layer can propagate into downstream analytics, reporting, and automated decisioning, so platform and data engineering owners should be engaged even though the direct technical impact is graded HIGH rather than critical. There is no public exploit identified at time of analysis and the flaw is not in CISA KEV, with EPSS at 0.6% (roughly the 45th percentile), so this is a managed remediation item rather than an emergency response.

Business Impact: Medium
Compensating Controls

Apply vendor patch (Apache StreamPark 2.1.6), subject to confirming current vendor advisory status given the conflicting patch data in the source context. Until the upgrade is validated: apply least privilege to StreamPark service accounts and job execution identities, restrict network access to the platform's management and API interfaces to trusted administrative networks, segment StreamPark hosts from sensitive downstream data stores, and alert on unexpected job launches or privilege-context changes.

Threat Intelligence Overview

EPSS Score
0.6%
Top 55% exploitable
Prevalence
Low
niche Apache stream-processing platform, limited enterprise deployment footprint
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Medium

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:a:apache:streampark:*:*:*:*:*:*:*:*
CVE-2025-54947 CRITICAL
9.8 Dec 12

Unauthenticated remote attackers can decrypt sensitive data or forge encrypted tokens in Apache StreamPark 2.0.0 through

CVE-2024-29070 CRITICAL
9.1 Jul 23

On versions before 2.1.4, session is not invalidated after logout. Rated critical severity (CVSS 9.1), this vulnerabilit

CVE-2024-29178 HIGH
8.8 Jul 18

On versions before 2.1.4, a user could log in and perform a template injection attack resulting in Remote Code Execution

CVE-2025-54981 HIGH
7.5 Dec 12

Apache StreamPark 2.0.0 through 2.1.6 encrypts sensitive authentication material, including JWT tokens, using AES in ECB

CVE-2023-49898 HIGH
7.2 Dec 15

In streampark, there is a project module that integrates Maven's compilation capability. Rated high severity (CVSS 7.2),

CVE-2024-34457 MEDIUM
6.5 Jul 22

On versions before 2.1.4, after a regular user successfully logs in, they can manually make a request using the authoriz

CVE-2025-53960 MEDIUM
5.9 Dec 12

Apache StreamPark 2.0.0 through 2.1.6 signs JSON Web Tokens using the user's own password as the HMAC (HS256) signing ke

CVE-2024-29120 MEDIUM
5.9 Jul 17

In Streampark (version < 2.1.4), when a user logged in successfully, the Backend service would return "Authorization" as

CVE-2023-30867 MEDIUM
4.9 Dec 15

In the Streampark platform, when users log in to the system and use certain features, some pages provide a name-based fu

CVE-2024-29737 MEDIUM
4.7 Jul 17

In streampark, the project module integrates Maven's compilation capabilities. Rated medium severity (CVSS 4.7), this vu

CVE-2024-48988 HIGH
7.6 Aug 22

SQL Injection vulnerability in Apache StreamPark.1.4 before 2.1.6. Rated high severity (CVSS 7.6), this vulnerability is

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy