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

> Attackers with read access can connect to arbitrary URLs using GitHub App credentials due to missing permission checks in the Jenkins plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-wg26-8wmj-cf9p

## What is CVE-2026-42522?

CVE-2026-42522 is a medium-severity missing authorization vulnerability in Jenkins GitHub Branch Source Plugin, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-42522?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:github-branch-source. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:github-branch-source` | Maven | All versions | 1967.1969.v205fd594c821 |
| `org.jenkins-ci.plugins:github-branch-source` | Maven | All versions | 1967.1969.v205fd594c821 |

Products: Jenkins Github Branch Source.

## How do I fix CVE-2026-42522?

Upgrade org.jenkins-ci.plugins:github-branch-source to 1967.1969.v205fd594c821 or later.

## Is CVE-2026-42522 being exploited?

There is no known exploitation of CVE-2026-42522 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins GitHub Branch Source Plugin

- [CVE-2024-23901](https://insights.sbomify.com/CVE-2024-23901/): Shared projects are unconditionally discovered by Jenkins GitLab Branch Source Plugin (medium 6.5)
- [CVE-2017-1000091](https://insights.sbomify.com/CVE-2017-1000091/): Jenkins GitHub Branch Source Plugin vulnerable to Cross-Site Request Forgery (medium 6.3)
- [CVE-2024-23903](https://insights.sbomify.com/CVE-2024-23903/): Non-constant time webhook token comparison in Jenkins GitLab Branch Source Plugin (medium 5.3)
- [CVE-2026-57285](https://insights.sbomify.com/CVE-2026-57285/): Jenkins GitHub Branch Source Plugin has missing permission check that allows enumerating GitHub Enterprise server URLs (medium 4.3)
- [CVE-2024-23902](https://insights.sbomify.com/CVE-2024-23902/): CSRF vulnerability in Jenkins GitLab Branch Source Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42522 and fix it if it is affected.

What it is: CVE-2026-42522 is a medium-severity missing authorization vulnerability in Jenkins GitHub Branch Source Plugin, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42522 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:github-branch-source (Maven): affected all versions; fixed in 1967.1969.v205fd594c821
- org.jenkins-ci.plugins:github-branch-source (Maven): affected all versions; fixed in 1967.1969.v205fd594c821

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42522/ (Markdown: https://insights.sbomify.com/CVE-2026-42522/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42522
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42522
- OSV: https://osv.dev/vulnerability/CVE-2026-42522

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42522/
Summaries are generated and may contain mistakes; the official description above is the record.