CVE-2022-36883: Lack of authentication mechanism in Jenkins Git Plugin webhook
Summary
CVE-2022-36883: Lack of authentication mechanism in Jenkins Git Plugin webhook. Affects org.jenkins-ci.plugins:git versions < 4.11.4. Fixed in 4.11.4. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins Git Plugin provides functionality for integrating Git repositories with Jenkins. It includes a webhook endpoint at /git/notifyCommit that allows users to notify Jenkins of changes to an SCM repository. This endpoint can be accessed via GET requests and does not require authentication in versions 4.11.3 and earlier. The endpoint also accepts a sha1 parameter to trigger immediate builds and checkout a specific commit. The output of the webhook endpoint reveals information about triggered or scheduled jobs, even those inaccessible to the user. Git Plugin 4.11.4 introduces a token parameter for authentication.
Vulnerability Detail
The lack of authentication in the Jenkins Git Plugin webhook endpoint allows attackers with knowledge of Git repository URLs to trigger builds of jobs using a specified Git repository and checkout an attacker-specified commit. Additionally, attackers can obtain information about the existence of jobs configured with the Git repository. This vulnerability poses a moderate risk (CVSS score: 6.5) and is assigned CWE-862.
How To Fix
Latest published version: 5.11.0 as of 23 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
4.11.4
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. Upgrading to the fixed version is the recommended solution.
Conclusion
The lack of authentication in the Jenkins Git Plugin webhook endpoint allows attackers to trigger builds and checkout specific commits, as well as obtain information about jobs configured with the Git repository. To mitigate this vulnerability, it is recommended to upgrade to Git Plugin version 4.11.4 or later. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:git →
FAQ
This vulnerability allows attackers to trigger builds and checkout specific commits in Jenkins jobs using a specified Git repository. It also exposes information about the existence of jobs configured with the Git repository.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Simply enter your pom.xml file, and Vulert will provide real-time alerts for open-source vulnerabilities.
Yes, starting from Git Plugin version 4.11.4, the webhook endpoint requires authentication using the token parameter.
Yes, this vulnerability can be exploited remotely by sending GET requests to the Git Plugin webhook endpoint without authentication.
The only known mitigation is to upgrade to Git Plugin version 4.11.4 or later, which introduces authentication for the webhook endpoint.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:git.
