CVE-2026-92122 Jenkins Project CVE debrief

Who should care

Defenders responsible for Jenkins deployments, particularly those using the Script Security Plugin, should assess exposure and apply remediation. This includes verifying the plugin version, restricting user permissions for defining and running sandboxed scripts, and monitoring for suspicious activity in the Jenkins controller JVM. Security teams and platform operators should prioritize updating to a fixed version of the plugin to prevent potential sandbox

Why it matters

CVE-2026-92122 is a high-severity vulnerability in Jenkins Script Security Plugin that allows attackers to bypass sandbox protection and execute arbitrary code. Defenders should verify exposure, restrict user permissions, and apply remediation.

• Potential sandbox bypass and arbitrary code execution in the context of the Jenkins controller JVM
• Possible exploitation by attackers with permission to define and run sandboxed scripts
• Need for verification of Jenkins Script Security Plugin version and exposure
• Priority on updating to a fixed version of the plugin

Technical summary

The Jenkins Script Security Plugin version 1415.v9a_f9b_3a_c253d and earlier does not properly check the method called through the proxy created when a sandboxed script coerces a value to an interface. This allows attackers with permission to define and run sandboxed scripts to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM. The vulnerability is a result of inadequate checks on the proxy created for sandboxed scripts, enabling potential attackers to execute code beyond the intended sandbox boundaries.

Defensive priority

Defenders should prioritize verifying exposure and applying remediation for Jenkins Script Security Plugin versions up to 1415.v9a_f9b_3a_c253d.

Recommended defensive actions

• Verify Jenkins Script Security Plugin version and update to a fixed version if necessary.
• Review and restrict permissions for users who can define and run sandboxed scripts.
• Monitor Jenkins controller JVM for suspicious activity.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Jenkins Script Security Plugin. The vendor advisory from Jenkins provides additional context. Evidence is limited to public sources, and defenders should verify exposure using official advisories and CVE records. The vulnerability allows attackers to bypass sandbox protection, potentially leading to arbitrary code execution in the Jenkins controller JVM context.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.