CVE-2026-48927
Description
Jenkins buildgraph-view Plugin 1.8 and earlier does not escape the build URL, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure jobs or views.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Jenkins buildgraph-view Plugin 1.8 and earlier has a stored XSS vulnerability via unescaped build URLs, exploitable by attackers who can configure jobs or views.
Vulnerability
Jenkins buildgraph-view Plugin version 1.8 and earlier fails to escape the build URL when rendering build information. This results in a stored cross-site scripting (XSS) vulnerability. The affected code path is reachable when the plugin displays builds in a view; no special configuration beyond installing the plugin is required for the vulnerability to exist. The issue is fixed in versions after 1.8 [1].
Exploitation
An attacker must have the ability to configure jobs or views in Jenkins. Such an attacker can inject malicious script content into a build URL, which is then stored and executed in the context of other users viewing the buildgraph view. No additional user interaction beyond viewing the affected view is required to trigger the XSS [1].
Impact
Successful exploitation allows the attacker to execute arbitrary JavaScript in the web browser of any user who views the compromised buildgraph view. This can lead to session hijacking, credential theft, or further actions within the Jenkins application under the victim's permissions. The impact is limited to the UI layer; direct compromise of the Jenkins controller is not achieved [1].
Mitigation
Jenkins has released a fix in a version after 1.8 of the buildgraph-view Plugin. Users should update to the latest version as specified in the Jenkins Security Advisory 2026-05-27 [1]. No workarounds are documented; updating the plugin is the recommended course of action.
AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=1.8
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Jenkins Security Advisory 2026-05-27Jenkins Security Advisories · May 27, 2026