dbcve.org
Templating EngineApplication · Jenkins

CVE-2025-31722

HIGH · 8.8 CVSS v3.1 Published 2025-04-02
Fix available
A fix is available. Upgrade to 2.5.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
In Jenkins Templating Engine Plugin 2.5.3 and earlier, libraries defined in folders are not subject to sandbox protection, allowing attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM.

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 Templating Engine Plugin versions 2.5.3 and earlier fails to enforce sandbox restrictions on libraries defined at the folder level. Attackers with Item/Configure permission can define malicious libraries within folders that bypass sandbox protection, enabling arbitrary code execution on the Jenkins controller JVM.

MitigationUpdate to a patched version of the Jenkins Templating Engine Plugin when available. Until then, restrict Item/Configure permission to trusted users only and review existing folder-level library definitions.

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
Templating EngineApplication
Affected:< 2.5.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 Jenkins Templating Engine plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | findstr -i templating
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version of Templating Engine plugin
    In Manage Jenkins > Manage Plugins > Installed, find 'Templating Engine' and note the Version column. Alternatively, check the plugin's manifest file in JENKINS_HOME/plugins/templating-engine/*.jpi (or .hpi) for the Version attribute.
    Affected if Version is 2.5.3 or earlier (anything below 2.5.4)
  3. Identify folder-level library configurations
    Navigate to a folder's configuration (click a folder > Configure) and look for the 'Library' section under 'Templating'. Alternatively, inspect JENKINS_HOME/jobs/*/config.xml for <library> elements inside folder-level configs.
    Affected if Any folder has one or more libraries configured in the Templating Engine Library section
  4. Confirm the library is actually used in pipelines
    Review Jenkinsfile or pipeline scripts in jobs within folders that have library configurations. Check if the library is referenced via '@Library' or imported in pipeline definitions.
    Affected if Pipelines within folders are using the folder-level templating libraries
  5. Check for Item/Configure permission assignment
    Review folder-level security matrix or role-based strategy permissions: Manage Jenkins > Manage and Assign Roles > Manage Roles (or Assign Roles). Look for users/groups granted 'Item/Configure' permission on folders.
    Affected if Any user or group has Item/Configure permission on folders that contain templating libraries

You are affected if the Templating Engine plugin version is below 2.5.4 AND folder-level libraries are configured in your Jenkins environment, regardless of whether those permissions are currently exploited.

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 2.5.4 or later
Fixed in 2.5.4
Interim mitigation

Update to a patched version of the Jenkins Templating Engine Plugin when available. Until then, restrict Item/Configure permission to trusted users only and review existing folder-level library definitions.

Recommended fix High confidence

Templating Engine Plugin version 2.5.4

  1. Back up your Jenkins configuration and data before updating any plugins
  2. Navigate to Manage Jenkins > Manage Plugins
  3. Go to the Updates tab or the Available tab and search for 'Templating Engine'
  4. Update the Templating Engine plugin to version 2.5.4 or later
  5. Restart the Jenkins controller as required for the plugin update to take effect
  6. Verify the plugin shows version 2.5.4 or higher in the installed plugins list

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

Fix this in Templating Engine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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