VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:github-branch-source: vulnerability history, versions and safety

org.jenkins-ci.plugins:github-branch-source is a package in the Maven ecosystem. Vulert records 5 vulnerabilities for it across 118 releases, from May 2022 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded M5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 24 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.jenkins-ci.plugins:github-branch-source vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:github-branch-source 1986.v801e40614d00 i

Updated on 23 Oct 2026

Good news: 1986.v801e40614d00, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

What to do: Stay on 1986.v801e40614d00 or newer. This can change: a vulnerability disclosed tomorrow can affect 1986.v801e40614d00 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1986.v801e40614d00 — unaffected i
  • Vulnerabilities on record 5 over 4 years · 2 in the last year i
  • Latest disclosure 24 Jun 2026 i
  • Highest CVSS 6.3 i
  • With no published fix 0 i
  • Stars 218 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.jenkins-ci.plugins:github-branch-source, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1986.v801e40614d00 12 Oct 2026 none MIT — Details →
1983.vfa_27ed961853 05 Aug 2026 none MIT — Details →
1967.1970.vd86979736546 15 Jun 2026 M1 MIT Yes Details →
1967.1969.v205fd594c821 22 Apr 2026 M1 MIT Yes Details →
1967.vdea_d580c1a_b_a_ 03 Feb 2026 M2 MIT Yes Details →
1936.vfa_a_5c2cef4e7 28 Jan 2026 M2 MIT Yes Details →
1934.v23cf60a_47fc3 12 Jan 2026 M2 MIT Yes Details →
1925.v62fb_7ffb_08ce 25 Nov 2025 M2 MIT Yes Details →
1917.v9ee8a_39b_3d0d 03 Nov 2025 M2 MIT Yes Details →
1911.vc09e01781005 25 Oct 2025 M2 MIT Yes Details →
1910.v4ca_b_2c639cb_0 23 Oct 2025 M2 MIT Yes Details →
1906.v21c5c13d25c6 15 Oct 2025 M2 MIT Yes Details →
1871.v50ffb_786515e 01 Oct 2025 M2 MIT Yes Details →
1869.vdb_846d75405b_ 26 Sep 2025 M2 MIT Yes Details →
1864.v411feec5e78e 17 Sep 2025 M2 MIT Yes Details →
1862.v1a_fc22a_d3788 11 Sep 2025 M2 MIT Yes Details →
1848.v42f74f7f4500 02 Sep 2025 M2 MIT Yes Details →
1844.v4a_9883d49126 28 Aug 2025 M2 MIT Yes Details →
1834.v857721ea_74c6 31 Jul 2025 M2 MIT Yes Details →
1833.v77b_6542df5a_8 30 Jul 2025 M2 MIT Yes Details →
1824.v046257273408 24 Jun 2025 M2 MIT Yes Details →
1822.v9eec8e5e69e3 30 May 2025 M2 MIT Yes Details →
1815.v9152b_2ff7a_1b_ 27 Mar 2025 M2 MIT Yes Details →
1810.v913311241fa_9 20 Jan 2025 M2 MIT Yes Details →
1809.v088b_5f22c768 14 Jan 2025 M2 MIT Yes Details →
1807.v50351eb_7dd13 23 Oct 2024 M2 MIT Yes Details →
1803.v98e3d8a_c8169 16 Oct 2024 M2 MIT Yes Details →
1797.v86fdb_4d57d43 20 Aug 2024 M2 MIT Yes Details →
1793.v1831e9c68d77 01 Aug 2024 M2 MIT Yes Details →
1790.v5a_7859812c8d 17 Jul 2024 M2 MIT Yes Details →
1789.v5b_0c0cea_18c3 02 May 2024 M2 MIT Yes Details →
1787.v8b_8cd49a_f8f1 11 Apr 2024 M2 MIT Yes Details →
1785.v99802b_69816c 27 Mar 2024 M2 MIT Yes Details →
1781.va_153cda_09d1b_ 11 Mar 2024 M2 MIT Yes Details →
2.0.3 13 Feb 2024 M5 MIT Yes Details →
1.6 13 Feb 2024 M5 MIT Yes Details →
2.0.1-beta-2 13 Feb 2024 M5 MIT Yes Details →
1.3 13 Feb 2024 M5 MIT Yes Details →
1694.vd46793a_c4a_57 13 Feb 2024 M2 MIT Yes Details →
2.2.3 13 Feb 2024 M3 MIT Yes Details →
2.11.1 13 Feb 2024 M2 MIT Yes Details →
2.5.1 13 Feb 2024 M2 MIT Yes Details →
2.7.0 13 Feb 2024 M2 MIT Yes Details →
1730.vff97c8a_1f804 13 Feb 2024 M2 MIT Yes Details →
2.2.0-alpha-4 13 Feb 2024 M3 MIT Yes Details →
2.9.2 13 Feb 2024 M2 MIT Yes Details →
2.3.1 13 Feb 2024 M3 MIT Yes Details →
1656.v77eddb_b_e95df 13 Feb 2024 M2 MIT Yes Details →
2.0.1-beta-6 13 Feb 2024 M5 MIT Yes Details →
2.9.1 13 Feb 2024 M2 MIT Yes Details →
1599.v9fb_798a_a_7c4f 13 Feb 2024 M2 MIT Yes Details →
2.4.0-beta-1 13 Feb 2024 M2 MIT Yes Details →
2.5.8 13 Feb 2024 M2 MIT Yes Details →
2.9.3 13 Feb 2024 M2 MIT Yes Details →
1.4-beta-1 13 Feb 2024 M5 MIT Yes Details →
2.10.0 13 Feb 2024 M2 MIT Yes Details →
2.0.7 13 Feb 2024 M5 MIT Yes Details →
0.1-beta-1 13 Feb 2024 M5 MIT Yes Details →
1687.v7618247e672d 13 Feb 2024 M2 MIT Yes Details →
2.2.0 13 Feb 2024 M3 MIT Yes Details →
2.0.2 13 Feb 2024 M5 MIT Yes Details →
2.0.0-beta-1 13 Feb 2024 M5 MIT Yes Details →
1696.v3a_7603564d04 13 Feb 2024 M2 MIT Yes Details →
2.9.6 13 Feb 2024 M2 MIT Yes Details →
2.10.1 13 Feb 2024 M2 MIT Yes Details →
2.4.2 13 Feb 2024 M2 MIT Yes Details →
2.0.1 13 Feb 2024 M5 MIT Yes Details →
2.7.1 13 Feb 2024 M2 MIT Yes Details →
1602.vfe89fe441b_36 13 Feb 2024 M2 MIT Yes Details →
1725.vd391eef681a_e 13 Feb 2024 M2 MIT Yes Details →
2.3.3 13 Feb 2024 M3 MIT Yes Details →
2.9.4 13 Feb 2024 M2 MIT Yes Details →
2.0.1-beta-1 13 Feb 2024 M5 MIT Yes Details →
2.4.5 13 Feb 2024 M2 MIT Yes Details →
1740.v51d5810e9e8c 13 Feb 2024 M2 MIT Yes Details →
1772.va_69eda_d018d4 13 Feb 2024 M2 MIT Yes Details →
2.4.6-beta-2 13 Feb 2024 M2 MIT Yes Details →
2.7.0-beta1 13 Feb 2024 M2 MIT Yes Details →
2.4.0 13 Feb 2024 M2 MIT Yes Details →
2.5.6 13 Feb 2024 M2 MIT Yes Details →
0.1-beta-3 13 Feb 2024 M5 MIT Yes Details →
2.4.3-beta-1 13 Feb 2024 M2 MIT Yes Details →
1.8 13 Feb 2024 M5 MIT Yes Details →
0.1-beta-2 13 Feb 2024 M5 MIT Yes Details →
1677.v731f745ea_0cf 13 Feb 2024 M2 MIT Yes Details →
2.2.0-beta-2 13 Feb 2024 M3 MIT Yes Details →
2.6.0 13 Feb 2024 M2 MIT Yes Details →
1.5 13 Feb 2024 M5 MIT Yes Details →
1637.vd833b_7ca_7654 13 Feb 2024 M2 MIT Yes Details →
1752.vc201a_0235d80 13 Feb 2024 M2 MIT Yes Details →
2.2.0-alpha-1 13 Feb 2024 M3 MIT Yes Details →
2.3.2 13 Feb 2024 M3 MIT Yes Details →
2.5.2 13 Feb 2024 M2 MIT Yes Details →
2.5.3 13 Feb 2024 M2 MIT Yes Details →
1728.v859147241f49 13 Feb 2024 M2 MIT Yes Details →
2.0.0 13 Feb 2024 M5 MIT Yes Details →
2.3.0 13 Feb 2024 M3 MIT Yes Details →
2.2.4 13 Feb 2024 M3 MIT Yes Details →
2.3.6 13 Feb 2024 M2 MIT Yes Details →
1.7 13 Feb 2024 M5 MIT Yes Details →
2.0.4-beta-1 13 Feb 2024 M5 — Yes Details →
2.11.4 13 Feb 2024 M2 — Yes Details →
2.2.0-alpha-2 13 Feb 2024 M3 — Yes Details →
2.5.0 13 Feb 2024 M2 — Yes Details →
2.9.5 13 Feb 2024 M2 — Yes Details →
1.10.1 13 Feb 2024 M5 — Yes Details →
2.0.1-beta-3 13 Feb 2024 M5 — Yes Details →
2.0.6 13 Feb 2024 M5 — Yes Details →
1758.v048414714f5d 13 Feb 2024 M2 — Yes Details →
2.2.0-alpha-3 13 Feb 2024 M3 — Yes Details →
2.2.5 13 Feb 2024 M3 — Yes Details →
2.0.0-beta-2 13 Feb 2024 M5 — Yes Details →
2.0.1-beta-5 13 Feb 2024 M5 — Yes Details →
2.3.4 13 Feb 2024 M3 — Yes Details →
2.9.7 13 Feb 2024 M2 — Yes Details →
2.2.6 13 Feb 2024 M3 — Yes Details →
2.8.2 13 Feb 2024 M2 — Yes Details →
2.9.9 13 Feb 2024 M2 — Yes Details →
1.1 13 Feb 2024 M5 — Yes Details →
1703.vd5a_2b_29c6cdc 13 Feb 2024 M2 — Yes Details →

The newest 120 of 166 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:github-branch-source

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000091: Jenkins GitHub Branch Source Plugin Cross-Site Request Forgery 6.3 medium 2.2.0-alpha-1 17 May 2022
CVE-2018-1000185: Jenkins GitHub Branch Source Plugin Server-Side Request Forgery 4.3 medium 2.3.5 14 May 2022
CVE-2017-1000087: Jenkins GitHub Branch Source Plugin Credential Enumeration 4.3 medium 2.2.0-alpha-1 17 May 2022
CVE-2026-42522: Jenkins GitHub Branch Source Plugin - Missing Permissions Check Allows Unauthorized Connection Tests 4.3 medium 1967.1969.v205fd594c821 29 Apr 2026
CVE-2026-57285: Jenkins GitHub Branch Source Plugin Missing Permission Check Vulnerability 4.3 medium 1967.1970 24 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.jenkins-ci.plugins:github-branch-source

Is org.jenkins-ci.plugins:github-branch-source safe to use?

Vulert records 5 vulnerabilities for org.jenkins-ci.plugins:github-branch-source in Maven: 0 critical, 0 high, 5 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.jenkins-ci.plugins:github-branch-source's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:github-branch-source 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.jenkins-ci.plugins:github-branch-source affected?

No. 1986.v801e40614d00, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.jenkins-ci.plugins:github-branch-source should I use?

1986.v801e40614d00 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.jenkins-ci.plugins:github-branch-source have?

5 vulnerabilities are recorded for org.jenkins-ci.plugins:github-branch-source in the Maven ecosystem: 0 critical, 0 high, 5 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.jenkins-ci.plugins:github-branch-source vulnerabilities disclosed?

2 vulnerabilities were recorded for org.jenkins-ci.plugins:github-branch-source in the last 12 months, and the oldest entry in this database dates to 14 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.jenkins-ci.plugins:github-branch-source are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.jenkins-ci.plugins:github-branch-source for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.jenkins-ci.plugins:github-branch-source version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.