Jenkins GitHub Branch Source Plugin vulnerable to Cross-Site Request ForgeryGHSA-w66r-f5gg-gqwm
MEDIUMGHSA-w66r-f5gg-gqwm is a medium-severity (CVSS 6.3) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:github-branch-source. A fix is available for org.jenkins-ci.plugins:github-branch-source — see the affected versions and patch details below.
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:github-branch-sourceReal-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
GitHub Branch Source Plugin connects to a user-specified GitHub API URL (e.g. GitHub Enterprise) as part of form validation and completion (e.g. to verify Scan Credentials are correct). This functionality improperly checked permissions, allowing any user with Overall/Read access to Jenkins to connect to any web server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery. An enumeration of credentials IDs in this plugin now requires the permission to have Extended Read permission (when that permission is enabled; otherwise Configure permission) to the job in whose context credentials are being accessed. If no job context exists, Overall/Administer permission is required.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:github-branch-source | all versions | 2.2.0-alpha-1org.jenkins-ci.plugins:github-branch-source:2.2.0-alpha-1 |
Affected Products
github branch sourcejenkinsDetection & 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:github-branch-source, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:github-branch-source to 2.2.0-alpha-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w66r-f5gg-gqwm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-w66r-f5gg-gqwm in your dependencies?
Find it across Maven, including transitive dependencies.