CVE-2020-2226 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:matrix-auth. A fix is available for org.jenkins-ci.plugins:matrix-auth — see the affected versions and patch details below.
Stored XSS vulnerability in Jenkins Matrix Authorization Strategy 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:matrix-authReal-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
Matrix Authorization Strategy Plugin 2.6.1 and earlier does not escape user names shown in the permission table. This results in a stored cross-site scripting (XSS) vulnerability. When using project-based matrix authorization, this vulnerability can be exploited by a user with Job/Configure or Agent/Configure permission, otherwise by users with Overall/Administer permission.
Matrix Authorization Strategy Plugin 2.6.2 escapes user names in the permission table.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:matrix-auth | all versions | 2.6.2org.jenkins-ci.plugins:matrix-auth:2.6.2 |
Affected Products
matrix authorization strategyjenkinsDetection & 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:matrix-auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:matrix-auth to 2.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2226 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-2-plugins-0:3.11.1597310986-1.el7 | RHSA-2020:3541 |
| Red Hat OpenShift Container Platform 4.3 | jenkins-2-plugins-0:4.3.1601981312-1.el7 | RHSA-2020:4265 |
| Red Hat OpenShift Container Platform 4.4 | jenkins-2-plugins-0:4.4.1598545590-1.el7 | RHSA-2020:3625 |
| Red Hat OpenShift Container Platform 4.5 | jenkins-2-plugins-0:4.5.1596698303-1.el7 | RHSA-2020:3453 |
| Red Hat OpenShift Container Platform 4.6 | openshift4/ose-aws-ebs-csi-driver-rhel8:v4.6.0-202010061132.p0 | RHBA-2020:4196 |
Frequently Asked Questions
Is CVE-2020-2226 in your dependencies?
Find it across Maven, including transitive dependencies.