Authenticated code execution via unsandboxed folder libraries
Published Apr 2, 2025 · Updated Feb 26, 2026
Code injection in Jenkins Templating Engine Plugin 2.5.3 and earlier allows remote authenticated users to execute code in the controller JVM. StepWrapperFactory compiles every library step with exec.getTrustedShell(), so folder-scoped Groovy supplied by Item/Configure users bypasses Script Security. Item/Configure permission on a folder is required; successful exploitation runs arbitrary code with the Jenkins controller's privileges.
Summary
What happened
Code injection in Jenkins Templating Engine Plugin 2.5.3 and earlier allows remote authenticated users to execute code in the controller JVM. StepWrapperFactory compiles every library step with exec.getTrustedShell(), so folder-scoped Groovy supplied by Item/Configure users bypasses Script Security. Item/Configure permission on a folder is required; successful exploitation runs arbitrary code with the Jenkins controller's privileges.
The record
- CVE
- CVE-2025-31722
- Published
- Apr 2, 2025
- Updated
- Feb 26, 2026
- Vendor
- Jenkins Project
- Product
- Jenkins Templating Engine Plugin
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 2, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo