XXE vulnerability in Jenkins DRY Plugin

published 2018-01-23 8y ago modified 2026-06-17 4mo ago also GHSA-x7qf-qh3r-mx22 , EUVD-2022-5740

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

Jenkins DRY Plugin 2.49 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

maven org.jvnet.hudson.plugins:dry 2.50

Is CVE-2018-1000010 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
maven	org.jvnet.hudson.plugins:dry	<2.50	2.50

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

References

jenkins.io /security/advisory/2018-01-22/
vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000010
advisory
jenkins.io /security/advisory/2018-01-22
web

Sources

Fencer Intel 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.