How severe is CVE-2021-29620?

CVE-2021-29620 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-29620?

CVE-2021-29620 affects the following packages: com.epam.reportportal:service-api (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-29620?

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 CVE-2021-29620 is resolved across your whole dependency graph.

How do I detect CVE-2021-29620 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 CVE-2021-29620 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 CVE-2021-29620 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-29620 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 CVE-2021-29620?

CVE-2021-29620 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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 CVE-2021-29620?

CVE-2021-29620 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 CVE-2021-29620 published, and has it been updated?

CVE-2021-29620 was published on June 23, 2021 and was last updated on October 24, 2026. 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

CVE-2021-29620 — service-api

HIGHFix: reportportal/service-api#1392

CVE-2021-29620 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

Also known asGHSA-24wf-7vf2-pv59

Published

Jun 23, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% 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

1 pkg affected

☕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

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

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

service-apireportportal

≥ 3.1.0 && < 5.4.0

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 5.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-29620 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

### 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/reportport

O3 Security · Impact-Aware SCA

Is CVE-2021-29620 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 23, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-29620

GHSA-24wf-7vf2-pv59

References

Advisorymvnrepository.com · service api Advisorynvd.nist.gov · CVE 2021 29620 Fixgithub.com · GHSA 24wf 7vf2 pv59 Fixgithub.com Webgithub.com · a73e0dfb4eda844c37139df1f9847013d55f084e

Related vulnerabilities

Also affects service-api

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

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

Same weakness: CWE-611

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

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

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-29620 — service-api

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Binaries

For more information

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-29620 in your dependencies?