CVE-2026-42522

MEDIUMNVD 4.34.3—

4.3

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.

CVSS v3: 4.3
EG Score: 4.3(medium)
EPSS: 7.1%
KEV: Not listed

Published

April 29, 2026

Last Modified

May 6, 2026

References (1)

jenkinsci-cert@googlegroupshttps://www.jenkins.io/security/advisory/2026-04-29/#SECURITY-3702

Affected Packages

(1 across 1 ecosystem)

Maven(1)

Package	Vulnerable range	Fixed in	Dependents
org.jenkins-ci.plugins:github-branch-source	0.1-beta-1 ... 2.9.9 (162 versions)	1967.1969.v205fd594c821	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-862Missing Authorization

Data Freshness Timeline

(refreshed 13× in last 7d / 19× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:44 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-23 00:08 UTCEG score recompute
2026-05-20 22:38 UTCepss_batch
2026-05-20 22:38 UTCepss_batch
2026-05-20 15:11 UTCEG score recompute
2026-05-20 11:22 UTCepss_batch
2026-05-20 11:22 UTCepss_batch

Frequently asked(5)

What is CVE-2026-42522?

CVE-2026-42522 is a medium vulnerability published on April 29, 2026. A missing permission check in Jenkins GitHub Branch Source Plugin 1967.vdead580c1aba and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL with attacker-specified GitHub App credentials.

When was CVE-2026-42522 disclosed?

CVE-2026-42522 was first published in the National Vulnerability Database on April 29, 2026, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-42522 actively exploited?

CVE-2026-42522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-42522?

CVE-2026-42522 has a CVSS v3 base score of 4.3 (NVD).

How do I remediate CVE-2026-42522?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42522, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42522

Explore →

Is Your Infrastructure Affected by CVE-2026-42522?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-42522

📅 Published

🔄 Last Modified

🔗 References (1)

Affected Packages

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2026-42522?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (1)

Frequently asked(5)

Related CVEs(same CWE)