CVE-2026-42522: Jenkins GitHub Branch Source Plugin: Missing permissions check allows attackers to perform a connection test

CVE-2026-42522 · Severity: medium · CVSS 4.3 · Published 2026-04-29

A missing permission check in Jenkins GitHub Branch Source Plugin 1967.vdea_d580c1a_b_a_ and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL with attacker-specified GitHub App credentials.

Technologies: org.jenkins-ci.plugins:github-branch-source (Maven). Vendors: Jenkins, Maven.

Quick answers

Is CVE-2026-42522 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-42522 being exploited in the wild.
How severe is CVE-2026-42522?
Medium severity, with a CVSS score of 4.3, published 29 April 2026.
Which products and versions are affected?
org.jenkins-ci.plugins:github-branch-source (Maven) ECOSYSTEM:introduced=0,fixed=1967.1969.v205fd594c821.
Is there a fix for CVE-2026-42522?
Yes. org.jenkins-ci.plugins:github-branch-source (Maven): upgrade to 1967.1969.v205fd594c821 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-42522?
Check whether you run Jenkins Github Branch Source or org.jenkins-ci.plugins:github-branch-source (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.plugins:github-branch-source (Maven): upgrade to 1967.1969.v205fd594c821 or later
    # set org.jenkins-ci.plugins:github-branch-source to 1967.1969.v205fd594c821 in your pom.xml or build.gradle

Affected products

  • Jenkins Github Branch Source
  • org.jenkins-ci.plugins:github-branch-source (Maven) ECOSYSTEM:introduced=0,fixed=1967.1969.v205fd594c821

Identifiers

  • CVE-2026-42522
  • GHSA-wg26-8wmj-cf9p

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.