CVE-2026-92131
Description
A flaw was found in the Jenkins Pipeline: Groovy Libraries Plugin. This vulnerability allows attackers who can configure Pipelines to exploit a path traversal issue. The plugin does not properly restrict library paths, enabling it to follow symbolic links outside the intended SCM checkout. This can lead to unauthorized reading of files in resource directories and deletion of files in test directories on the Jenkins controller file system.
Statement
A path traversal flaw was found in the Jenkins Pipeline: Groovy Libraries Plugin (pipeline-groovy-lib). Versions 805.va_fc79344957d and earlier do not restrict the library path provided to the library Pipeline step to a relative path inside the SCM checkout and follow symbolic links to locations outside of the SCM checkout when retrieving the library, allowing attackers able to configure Pipelines (Item/Configure-level access on the Jenkins controller) to read files in a resources directory and to delete files in a test directory on the Jenkins controller file system. The vulnerable plugin is bundled at 752.vdddedf804e72 (within the affected range) in the jenkins-2-plugins RPM shipped in the OpenShift Jenkins images for ocp-tools-4.12 through 4.19. The upstream fix is pipeline-groovy-lib 806.v408277b_33d1d.
Mitigation
Upgrade the bundled pipeline-groovy-lib plugin to 806.v408277b_33d1d or later. A bundle bump to 822 is in flight via JKNS-1291/JKNS-1292 but has not yet shipped in the ocp-tools-4 jenkins-2-plugins streams. As an interim measure, restrict the ability to configure Pipelines (Item/Configure-level permission) on the Jenkins controller to trusted users.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
