GitHubApplication · Jenkins
CVE-2026-42523
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins GitHub Plugin 1.46.0 and earlier contains a stored XSS vulnerability where the current job URL is improperly sanitized when used in JavaScript validation for the 'GitHub hook trigger for GITScm polling' feature. Attackers with Overall/Read permission can inject malicious JavaScript that executes in the browsers of other users viewing the affected job configuration pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitHubApplication
< 1.46.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of the GitHub PluginNavigate to Manage Jenkins > Manage Plugins > Installed tab and locate 'GitHub' plugin in the list. Alternatively, access /pluginManager/pluginInformation/github in your Jenkins URL to view plugin details.Affected if The installed version is 1.46.0 or earlier, or less than 1.46.0.1.
-
Determine if the GitHub hook trigger for GITScm polling feature is in useReview your Jenkins job configurations. Check each job's configuration page for the 'GitHub hook trigger for GITScm polling' checkbox under the 'Build Triggers' section.Affected if Any job has the 'GitHub hook trigger for GITScm polling' option enabled.
-
Inspect the job configuration for unsanitized URL handlingView the source of a job configuration page that has the GitHub hook trigger enabled. Look for JavaScript validation code that references the current job URL. Inspect the DOM or view the page source to see if the job URL appears in an unescaped context within JavaScript code.Affected if The job URL appears in raw or unescaped form within inline JavaScript validation logic on the configuration page.
-
Verify user permissions that allow job configuration accessNavigate to Manage Jenkins > Manage and Assign Roles to review which users or groups have Overall/Read permission and the ability to configure jobs.Affected if Users with Overall/Read permission (or equivalent job configuration access) exist in the system.
You are affected if the GitHub Plugin version is below 1.46.0.1 AND the 'GitHub hook trigger for GITScm polling' feature is enabled on any job, as the XSS only triggers when users view those specific job configuration pages.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.46.0.1
Upgrade to Jenkins GitHub Plugin version 1.46.1 or later which properly sanitizes the job URL output in the JavaScript validation logic.
GitHub Plugin version 1.46.0.1 or later
- 1. Log in to Jenkins with administrator credentials
- 2. Navigate to 'Manage Jenkins' from the left sidebar
- 3. Click on 'Manage Plugins'
- 4. Select the 'Updates' tab
- 5. Locate the 'GitHub' plugin in the list of available updates
- 6. Check the box next to the GitHub plugin
- 7. Click 'Download now and install after restart'
- 8. Wait for the download to complete
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitHub
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42523 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data