CVE-2021-21659 — urltrigger
HIGHCVE-2021-21659 is a high-severity (CVSS 8.1) vulnerability in org.jenkins-ci.plugins:urltrigger. EPSS puts its 30-day exploitation probability at 66.8% (99th percentile). A fix is available for org.jenkins-ci.plugins:urltrigger — see the affected versions and patch details below.
XXE vulnerability in Jenkins URLTrigger Plugin
EPSS Exploitation Probability
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
org.jenkins-ci.plugins:urltriggerReal-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
Jenkins URLTrigger Plugin 0.48 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
This allows attackers with Job/Configure permission or otherwise able to control the contents of an URL to an XML document being examined for changes to have Jenkins parse a crafted XML document that uses external entities for extraction of secrets from the polling Jenkins controller or agent, server-side request forgery, or denial-of-service attacks.
UJenkins RLTrigger Plugin 0.49 disables external entity resolution for its XML parser.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:urltrigger | all versions | 0.49org.jenkins-ci.plugins:urltrigger:0.49 |
Affected Products
urltriggerjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:urltrigger, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:urltrigger to 0.49 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21659 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
Is CVE-2021-21659 in your dependencies?
Find it across Maven, including transitive dependencies.