Improper Restriction of XML External Entity Reference in Jenkins JUnit Plugin

published 2018-02-09 8 y ago modified 2026-06-17 4 mo ago also GHSA-4rj6-9pjh-882r , EUVD-2022-2441

cvss: 8.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

Jenkins JUnit Plugin 1.23 and earlier processes XML external entities in files it parses as part of the build process, allowing attackers with user permissions in Jenkins to extract secrets from the Jenkins master, perform server-side request forgery, or denial-of-service attacks.

Patch / fix

fixed in 1 links 1

maven org.jenkins-ci.plugins:junit 1.24

github.com/jenkinsci/junit-plugin@15f39fc commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000056 updated 2025-11-21 cvss 7.1

jenkins-plugin-junit: XML External Entity (XXE) via a maliciously crafted file

Red Hat OpenShift Enterprise 3 jenkins-plugin-junit
affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.3	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub	3.0	8.3	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:junit	<1.24	1.24

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference
CWE-918 Server-Side Request Forgery

References

github.com /jenkinsci/junit-plugin/commit/15f39fc49d9f25bca872badb48e708a8bb815ea7
web
jenkins.io /security/advisory/2018-02-05/
vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000056
advisory
github.com /jenkinsci/junit-plugin
package
jenkins.io /security/advisory/2018-02-05
web

Sources

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.

Summary