GHSA-24wf-7vf2-pv59 is a high-severity (CVSS 7.5) XML External Entity (XXE) vulnerability in com.epam.reportportal:service-api. A fix is available for com.epam.reportportal:service-api — see the affected versions and patch details below.
XXE vulnerability on Launch import with externally-defined DTD file
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-24wf-7vf2-pv59 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.epam.reportportal:service-apiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Starting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file which imports external Document Type Definition (DTD) file with external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.
Patches
Fixed with: https://github.com/reportportal/service-api/pull/1392
Binaries
docker pull reportportal/service-api:5.4.0
https://github.com/reportportal/service-api/packages/846871?version=5.4.0
For more information
If you have any questions or comments about this advisory email us: [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.epam.reportportal:service-api | ≥ 3.1.0&&< 5.4.0 | 5.4.0com.epam.reportportal:service-api:5.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.epam.reportportal:service-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.epam.reportportal:service-api to 5.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-24wf-7vf2-pv59 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-24wf-7vf2-pv59 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-24wf-7vf2-pv59. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-24wf-7vf2-pv59 in your dependencies?
O3 Security finds GHSA-24wf-7vf2-pv59 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.