How severe is GHSA-2jx8-v4hv-gx3h?

GHSA-2jx8-v4hv-gx3h has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2jx8-v4hv-gx3h?

GHSA-2jx8-v4hv-gx3h affects the following packages: com.epam.reportportal:service-api (Maven), com.epam.reportportal:service-api (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2jx8-v4hv-gx3h?

Update com.epam.reportportal:service-api to 4.3.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx8-v4hv-gx3h is resolved across your whole dependency graph.

How do I detect GHSA-2jx8-v4hv-gx3h in my Maven dependencies?

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.

How do I mitigate GHSA-2jx8-v4hv-gx3h if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-2jx8-v4hv-gx3h actively exploited in the wild?

No public exploit code has been indexed for GHSA-2jx8-v4hv-gx3h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2jx8-v4hv-gx3h?

GHSA-2jx8-v4hv-gx3h has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2jx8-v4hv-gx3h?

GHSA-2jx8-v4hv-gx3h is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2jx8-v4hv-gx3h published, and has it been updated?

GHSA-2jx8-v4hv-gx3h was published on June 28, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

XXE vulnerability in Launch importGHSA-2jx8-v4hv-gx3h

HIGHFix: reportportal/service-api#1201

GHSA-2jx8-v4hv-gx3h 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.

Also known asCVE-2020-12642

Published

Jun 28, 2021

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕com.epam.reportportal:service-api☕com.epam.reportportal:service-api

Real-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

Release Date	Affected Projects	Affected Versions	Access Vector	Security Risk
Monday, May 4, 2020	service-api	Every version, starting from 3.1.0	Remote	Medium

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 that uses external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.

Report Portal versions 4.3.12+ and 5.1.1+ disables external entity resolution for theirs XML parser.

We advise our users install the latest releases we built specifically to address this issue.

Patches

Fixed with https://github.com/reportportal/service-api/pull/1201

Binary Download

https://bintray.com/epam/reportportal/service-api/5.1.1 https://bintray.com/epam/reportportal/service-api/4.3.12

Docker Container Download

RP v4: docker pull reportportal/service-api:4.3.12
RP v5: docker pull reportportal/service-api:5.1.1

Acknowledgement

The issue was reported to Report Portal Team by an external security researcher. Our Team thanks Julien M. for reporting the issue.

For more information

If you have any questions or comments about this advisory email us: [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.epam.reportportal:service-api`	≥ 3.1.0&&< 4.3.12	4.3.12`com.epam.reportportal:service-api:4.3.12`
☕Maven	`com.epam.reportportal:service-api`	≥ 5.0.0&&< 5.1.1	5.1.1`com.epam.reportportal:service-api:5.1.1`

Affected Products

1 product · 2 configurations

Application

service-apireportportal

≥ 5.0.0 && < 5.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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 4.3.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx8-v4hv-gx3h is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

| Release Date | Affected Projects | Affected Versions | Access Vector| Security Risk | |--------------|-------------------|-------------------|---------------|---------------| | Monday, May 4, 2020| [service-api](https://github.com/reportportal/service-api) | Every version, starting from 3.1.0 | Remote | Medium | ### 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 that uses external entities

O3 Security · Impact-Aware SCA

Is GHSA-2jx8-v4hv-gx3h in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-611XML External Entity (XXE)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

reportportal

6.2/10

Maintained10/10

Code-Review6/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Jun 28, 2021

Last updated

Nov 8, 2023

Identifiers

GHSA-2jx8-v4hv-gx3h

References

Advisorynvd.nist.gov · CVE 2020 12642 Webgithub.com · GHSA 2jx8 v4hv gx3h Webgithub.com Webgithub.com · da4a012abdcc69f02f4255d81466f1f473b7f418 Packagegithub.com · reportportal

Related vulnerabilities

Also affects service-api

This CVE is high severity; 3 of 4 other CVEs affecting service-api are rated as high or higher (top: high).

CVE-2023-25822GHSA-7qfm-6m33-rgg9CVE-2021-29620CVE-2020-12642

Same weakness: CWE-611

This CVE is high severity; 4 of 4 other CVEs with CWE-611 are rated as high or higher (top: critical).

CVE-2026-108358CVE-2026-108357CVE-2026-61586CVE-2026-61741Browse all CWE-611

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023

XXE vulnerability in Launch importGHSA-2jx8-v4hv-gx3h

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Binary Download

Docker Container Download

Acknowledgement

For more information

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-2jx8-v4hv-gx3h in your dependencies?