GitHub vulnerabilitiesRanked by how likely they are to be used.
GitHub is made by Jenkins. We track 5 published vulnerabilities listed under that exact name, across 69 versions. None of them is on the list of flaws known to be exploited today. Jenkins lists newer releases under their own names, such as Github Branch Source, so check those pages too.
We keep watching the known-exploited list.
Is GitHub listed under other names? Yes.
Jenkins also lists GitHub under more specific names, such as Github Branch Source and Github Pull Request Builder. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which GitHub vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of GitHub's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which GitHub flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 91%CVE-2018-1000600High
A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCredentialsCreator.java that allows attackers to an attacker-specified URL using attacker-specified...
- 1.0%CVE-2018-1000183Medium
A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.0 and older in GitHubServerConfig.java that allows attackers with Overall/Read access to connect to an attacker-specified URL...
- 0.9%CVE-2022-36885Medium
Jenkins GitHub Plugin 1.34.4 and earlier uses a non-constant time comparison function when checking whether the provided and computed webhook signatures are equal, allowing attackers to use statistical methods to...
- 0.6%CVE-2018-1000184Medium
A server-side request forgery vulnerability exists in Jenkins GitHub Plugin 1.29.0 and older in GitHubPluginConfig.java that allows attackers with Overall/Read access to cause Jenkins to send a GET request to a...
- 0.6%CVE-2023-46650Medium
Jenkins GitHub Plugin 1.37.3 and earlier does not escape the GitHub project URL on the build page when showing changes, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with...
- 0.5%CVE-2026-42523Critical
Jenkins GitHub Plugin 1.46.0 and earlier improperly processes the current job URL as part of JavaScript implementing validation of the feature "GitHub hook trigger for GITScm polling", resulting in a stored...
Running GitHub? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCredentialsCreator.java that allows attackers to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
- Matched to
- GitHub on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name GitHub, across 69 versions.
None of GitHub's vulnerabilities is on the list of flaws known to be exploited today.
Jenkins also lists GitHub under more specific names, such as Github Branch Source and Github Pull Request Builder. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track GitHub. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.