CVE-2025-30001

HIGHNVD 7.37.3—Trending — 3 sources updated this week

7.3

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.

CVSS v3: 7.3
EG Score: 7.3(medium)
EPSS: 50.8%
KEV: Not listed

Published

October 10, 2025

Last Modified

November 4, 2025

References (2)

security@apachehttps://lists.apache.org/thread/xfmsvhkcnr1831n0w5ovy3p44lsmfb7m
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2025/09/04/1

Patch Availability(1)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
maven	org.apache.streampark:streampark	—	ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-279

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 21:05 UTCEG score recompute
2026-05-29 21:05 UTCGHSA enrichment
2026-05-29 13:44 UTCepss_batch

Frequently asked(5)

What is CVE-2025-30001?

CVE-2025-30001 is a high vulnerability published on October 10, 2025. 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.

When was CVE-2025-30001 disclosed?

CVE-2025-30001 was first published in the National Vulnerability Database on October 10, 2025, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2025-30001 actively exploited?

CVE-2025-30001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2025-30001?

CVE-2025-30001 has a CVSS v3 base score of 7.3 (NVD).

How do I remediate CVE-2025-30001?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-30001, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-30001

Explore →

Is Your Infrastructure Affected by CVE-2025-30001?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2025-30001

📅 Published

🔄 Last Modified

🔗 References (2)

Patch Availability(1)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2025-30001?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)