CVE-2026-42523: Jenkins GitHub Plugin 1.46.0 and earlier improperly processes the current job URL as part of JavaScript implem

Q: How do I fix CVE-2026-42523?

github: upgrade to 1.46.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-42523 being exploited?

CVE-2026-42523 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-42523 affect?

CVE-2026-42523 affects github. Severity is critical (CVSS 9.0). 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 cross-site scripting (XSS) vulner

Q: How urgent is CVE-2026-42523?

Priority 37/100. Critical severity

This month

CRITICAL 9.0UPGRADE

CVE-2026-42523 is a critical-severity flaw (CVSS 9.0) affecting github. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 cross-site scripting (XSS) vulnerability exploitable by non-anonymous attackers with Overall/Read permission.

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-04-29
Last modified	2026-10-26

Publisher (CNA): Jenkins Project · Vendor: jenkins

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-29 14:16 UTCPublished CVE record published
2026-10-26 20:10 UTCUpdated Record last modified

jenkins github UPGRADE

Affected: < 1.46.0.1

Fixed in: 1.46.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy github || rpm -q github || github --version

2. UPGRADE to 1.46.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade github

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade github

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-42523?

github: upgrade to 1.46.0.1. Exact commands for each OS are on this page.

Is CVE-2026-42523 being exploited?

CVE-2026-42523 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-42523 affect?

CVE-2026-42523 affects github. Severity is critical (CVSS 9.0). 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 cross-site scripting (XSS) vulner

How urgent is CVE-2026-42523?

Priority 37/100. Critical severity

Software pages

Jenkins vulnerabilities · GitHub vulnerabilities

References

← Back to latest CVEs