CVE-2022-25598 json
Apache DolphinScheduler user registration is vulnerable to ReDoS attacks
published 2022-03-30 4 y ago modified 2026-06-17 4 mo ago also GHSA-qg5x-66hp-cw5p , PYSEC-2022-176 , EUVD-2022-0021
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Apache DolphinScheduler user registration is vulnerable to Regular express Denial of Service (ReDoS) attacks, Apache DolphinScheduler users should upgrade to version 2.0.5 or higher.
Patch / fix
- maven org.apache.dolphinscheduler:dolphinscheduler 2.0.5
- pypi apache-dolphinscheduler 2.0.5
- Apache Software Foundation Apache DolphinScheduler 2.0.5
Exploit prediction
1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.dolphinscheduler:dolphinscheduler | <2.0.5 |
2.0.5 |
| pypi | apache-dolphinscheduler | <2.0.5 |
2.0.5 |
Affected products
- Apache Software Foundation Apache DolphinScheduler
Classification
References
-
lists.apache.org
/thread/hwnw7xr969sg5nv84wz75nfr2c76fl93
web, mailing-list, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-25598
advisory
-
github.com
/apache/dolphinscheduler
package
-
github.com
/pypa/advisory-database/tree/main/vulns/apache-dolphinscheduler/PYSEC-2022-176.yaml
web
-
github.com
/advisories/GHSA-qg5x-66hp-cw5p
advisory
Sources
- CVE List CVE-2022-25598
- GitHub Advisory GHSA-qg5x-66hp-cw5p
- NVD CVE-2022-25598
- OSV PYSEC-2022-176
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.