dbcve.org
Buildgraph ViewApplication · Jenkins

CVE-2026-48927

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 1.8 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
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.

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 confidence

The Jenkins buildgraph-view Plugin versions 1.8 and earlier fails to properly escape/sanitize build URLs before rendering them in the plugin's UI, creating a stored cross-site scripting (XSS) vulnerability. Attackers with the ability to configure jobs or views can inject malicious JavaScript code into build URLs that will execute in the browsers of other users viewing the buildgraph.

MitigationUpdate the buildgraph-view Plugin to a version newer than 1.8 when available. Until a patch is released, restrict job and view configuration permissions to trusted users only, or temporarily disable the plugin if not essential.

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
Buildgraph ViewApplication
Affected:<= 1.8

CVSS 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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm buildgraph-view plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli or check $JENKINS_HOME/plugins for buildgraph-view directory
    Affected if The plugin is present in the Jenkins plugins directory or plugin manager
  2. Identify installed plugin version
    Look for the version file inside the buildgraph-view plugin directory (e.g., $JENKINS_HOME/plugins/buildgraph-view/META-INF/MANIFEST.MF or the Jenkins plugin manager UI showing the version)
    Affected if The version listed is 1.8 or any version lower than 1.8
  3. Check for active usage of buildgraph-view
    Review Jenkins views and dashboards to see if any views are configured to use the buildgraph-view plugin, or check job configurations for buildgraph-related views
    Affected if Any views or job configurations reference or display buildgraph-view output
  4. Assess who can configure jobs or views
    Navigate to Manage Jenkins > Manage and Assign Roles, or review matrix-based security settings to see which users or groups have Job/View Configure permissions
    Affected if Users with limited or untrusted permissions (beyond administrators) have the ability to configure jobs or views

A user is affected if the buildgraph-view plugin is installed at version 1.8 or lower AND the plugin is actively in use or can be configured by non-administrative users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.8
Interim mitigation

Update the buildgraph-view Plugin to a version newer than 1.8 when available. Until a patch is released, restrict job and view configuration permissions to trusted users only, or temporarily disable the plugin if not essential.

Recommended fix Moderate confidence

buildgraph-view plugin version > 1.8 (check Jenkins Update Center for latest available version)

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Locate the 'buildgraph-view' plugin in the list
  5. 5. If an update is available, click 'Update' to install the latest version
  6. 6. After updating, restart Jenkins if required
  7. 7. Verify the plugin is updated to a version newer than 1.8

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Buildgraph View Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48927 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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