How severe is CVE-2020-2172?

CVE-2020-2172 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-2172?

CVE-2020-2172 affects the following packages: io.jenkins.plugins:code-coverage-api (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2172?

Update io.jenkins.plugins:code-coverage-api to 1.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2172 is resolved across your whole dependency graph.

How do I detect CVE-2020-2172 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:code-coverage-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-2172 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-2020-2172 actively exploited in the wild?

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

CVE-2020-2172 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-2020-2172?

CVE-2020-2172 is classified as CWE-776 (CWE-776). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-2172 published, and has it been updated?

CVE-2020-2172 was published on April 7, 2020 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

MEDIUM severity

CVE-2020-2172 — code-coverage-api

MEDIUMFix: jenkinsci/code-coverage-api-plugin@f0ef84c

CVE-2020-2172 is a medium-severity (CVSS 6.5) CWE-776 vulnerability in io.jenkins.plugins:code-coverage-api. A fix is available for io.jenkins.plugins:code-coverage-api — see the affected versions and patch details below.

XXE vulnerability in Jenkins Code Coverage API Plugin

Also known asGHSA-cmgm-q8hf-p7jc

Published

Apr 7, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕io.jenkins.plugins:code-coverage-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

Code Coverage API Plugin 1.1.4 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. This allows a user able to control the input files for the "Publish Coverage Report" post-build step to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.

Code Coverage API Plugin 1.1.5 disables external entity resolution for its XML parser.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:code-coverage-api`	all versions	1.1.5`io.jenkins.plugins:code-coverage-api:1.1.5`

Affected Products

1 product · 1 configurations

Application

code coverage apijenkins

≤ 1.1.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:code-coverage-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:code-coverage-api to 1.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2172 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

Code Coverage API Plugin 1.1.4 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. This allows a user able to control the input files for the \"Publish Coverage Report\" post-build step to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery. Code Coverage API Plugin 1.1.5 disables external entity resolution for its XML parser.

O3 Security · Impact-Aware SCA

Is CVE-2020-2172 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-776CWE-776

Weaponization

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

Timeline

Disclosed

Apr 7, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2172

GHSA-cmgm-q8hf-p7jc

References

Advisoryjenkins.io · 2020 04 07 Advisorynvd.nist.gov · CVE 2020 2172 Webopenwall.com Webgithub.com · f0ef84c25f7bc4de4e722e994de57d238225834c Packagegithub.com · code coverage api plugin

Related vulnerabilities

Also affects code-coverage-api

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

CVE-2021-21677CVE-2020-2106

Same weakness: CWE-776

This CVE is medium severity; 6 of 6 other CVEs with CWE-776 are rated as high or higher (top: high).

CVE-2026-108358CVE-2026-108357CVE-2026-78681CVE-2026-73569CVE-2026-54077CVE-2026-12993Browse all CWE-776

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2172 — code-coverage-api

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2020-2172 in your dependencies?