CVE-2026-42523: Vulnerability in Jenkins Project Jenkins GitHub Plugin
Jenkins GitHub Plugin versions 1. 46. 0 and earlier contain a stored cross-site scripting (XSS) vulnerability. This occurs because the plugin improperly processes the current job URL within JavaScript used for validating the 'GitHub hook trigger for GITScm polling' feature. The vulnerability can be exploited by non-anonymous users who have Overall/Read permission in Jenkins.
AI Analysis
Technical Summary
The Jenkins GitHub Plugin up to version 1.46.0 improperly handles the current job URL in JavaScript validation code for the GitHub hook trigger feature. This flaw allows stored cross-site scripting (XSS) attacks, where malicious script code can be injected and executed in the context of Jenkins. Exploitation requires the attacker to have non-anonymous access with Overall/Read permissions, limiting the attack surface to authenticated users with at least read-level privileges.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker with Overall/Read permissions to execute arbitrary JavaScript in the context of Jenkins users' browsers. This could lead to session hijacking, unauthorized actions, or other malicious activities within the Jenkins environment. However, exploitation requires authenticated access, which reduces the risk from anonymous or external attackers.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Overall/Read permissions to trusted users only and monitor for suspicious activity related to the GitHub hook trigger feature. Avoid enabling the vulnerable feature if possible.
CVE-2026-42523: Vulnerability in Jenkins Project Jenkins GitHub Plugin
Description
Jenkins GitHub Plugin versions 1. 46. 0 and earlier contain a stored cross-site scripting (XSS) vulnerability. This occurs because the plugin improperly processes the current job URL within JavaScript used for validating the 'GitHub hook trigger for GITScm polling' feature. The vulnerability can be exploited by non-anonymous users who have Overall/Read permission in Jenkins.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Jenkins GitHub Plugin up to version 1.46.0 improperly handles the current job URL in JavaScript validation code for the GitHub hook trigger feature. This flaw allows stored cross-site scripting (XSS) attacks, where malicious script code can be injected and executed in the context of Jenkins. Exploitation requires the attacker to have non-anonymous access with Overall/Read permissions, limiting the attack surface to authenticated users with at least read-level privileges.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker with Overall/Read permissions to execute arbitrary JavaScript in the context of Jenkins users' browsers. This could lead to session hijacking, unauthorized actions, or other malicious activities within the Jenkins environment. However, exploitation requires authenticated access, which reduces the risk from anonymous or external attackers.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Overall/Read permissions to trusted users only and monitor for suspicious activity related to the GitHub hook trigger feature. Avoid enabling the vulnerable feature if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- jenkins
- Date Reserved
- 2026-04-28T09:24:35.048Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f20cdfcbff5d8610181a8a
Added to database: 4/29/2026, 1:51:27 PM
Last enriched: 4/29/2026, 2:06:42 PM
Last updated: 4/29/2026, 2:52:14 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.