dbcve.org
Pipeline\Application · Jenkins

CVE-2026-48921

HIGH · 7.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 798.v5cc688825312 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier does not prohibit symbolic links in shared libraries, allowing attackers able to control the content of a library used by a Pipeline job to read arbitrary files on the Jenkins controller filesystem.

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 Pipeline: Groovy Libraries Plugin versions 797.v90ea_a_9b_e45a_0 and earlier fails to validate or prohibit symbolic links within shared libraries. An attacker who can control the content of a library used by a Pipeline job can create symlinks pointing to arbitrary files outside the intended library directory, enabling arbitrary file read on the Jenkins controller filesystem.

MitigationUpdate the Groovy Libraries Plugin to a version that prohibits symbolic links in shared libraries, and audit library configurations to restrict who can define or modify shared library content.

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
Pipeline\Application
Affected:< 798.v5cc688825312

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/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 checks

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

  1. Verify Groovy Libraries Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline: Groovy Libraries' to view the installed version, or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugins/ directory for the plugin version manifest)
    Affected if The installed version is 797.v90ea_a_9b_e45a_0 or earlier (versions prior to 798.v5cc688825312)
  2. Confirm shared libraries are configured
    Navigate to Manage Jenkins > System > Global Pipeline Libraries, or check the Jenkins configuration file (jenkins.model.Jenkins.location.config.xml and related) for library definitions
    Affected if One or more shared libraries are defined and configured in Jenkins
  3. Check library repository access permissions
    Review the credentials and SCM configuration for each defined shared library to identify which users or roles can modify library content in the source repository
    Affected if Users with pipeline edit permissions or library contributors can push changes to the library repository without restriction
  4. Inspect library repositories for symlinks
    Clone or review the source repositories containing shared library code and check for symbolic links (using 'ls -la' or 'find . -type l' in the repository)
    Affected if Symbolic links exist in any shared library repository pointing to files outside the library directory tree

You are affected if the Groovy Libraries Plugin version is 797.v90ea_a_9b_e45a_0 or earlier AND shared libraries are configured, especially if untrusted users can modify library content or symlinks already exist in library repositories.

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 798.v5cc688825312 or later
Fixed in 798.v5cc688825312
Interim mitigation

Update the Groovy Libraries Plugin to a version that prohibits symbolic links in shared libraries, and audit library configurations to restrict who can define or modify shared library content.

Recommended fix High confidence

Pipeline: Groovy Libraries Plugin version 798.v5cc688825312 or later

  1. 1. In the Jenkins web UI, go to 'Manage Jenkins' > 'Manage Plugins'
  2. 2. Click on the 'Updates' tab
  3. 3. Search for 'Pipeline: Groovy Libraries' or 'Groovy Libraries'
  4. 4. Select the plugin and click 'Download now and install after restart'
  5. 5. Wait for the plugin to download, then check 'Restart Jenkins' to complete the installation
  6. 6. After Jenkins restarts, verify the plugin version is 798.v5cc688825312 or higher under 'Manage Plugins' > 'Installed'

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

Fix this in Pipeline\ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48921 — 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-48921 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