Apache StreamPark Path Traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-45802: 1.31% estimated exploitation activity in the next 30 days; percentile 70.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Streampark allows any users to upload a jar as application, but there is no mandatory verification of the uploaded file type. This means users may upload some high-risk files, and may upload them to any directory. Users of the affected versions should upgrade to Apache StreamPark 2.0.0 or later.

Published by the source

6 Jul 2023, 19:24 UTC

Last modified by the source

21 Oct 2024, 19:06 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6874-289g-f7h7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-45802

Advisory: Apache StreamPark Path Traversal vulnerability
IDs: CVE-2022-45802, GHSA-6874-289g-f7h7
Record: https://patchnext.com/advisories/cve-2022-45802 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.streampark:streampark-common_2.12 2.0.0; org.apache.streampark:streampark-common_2.11 2.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.streampark:streampark-common_2.12: affected < 2.0.0; fixed in 2.0.0
- Maven org.apache.streampark:streampark-common_2.11: affected < 2.0.0; fixed in 2.0.0

## Suggested inspection (read-only)
- Maven org.apache.streampark:streampark-common_2.12: check the installed version with your package manager.
- Maven org.apache.streampark:streampark-common_2.11: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.streampark:streampark-common_2.12, org.apache.streampark:streampark-common_2.11.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6874-289g-f7h7 (GitHub-reviewed advisory GHSA-6874-289g-f7h7 lists affected ranges: Maven org.apache.streampark:streampark-common_2.12 >=0 =0 <2.0.0)

Commands are suggestions: review each one before running it.