PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-92125 Jenkins Project CVE debrief

CVE-2026-92125 debrief based on the supplied source corpus. The vulnerability is in the Jenkins Script Security Plugin, specifically in versions up to 1415.v9a_f9b_3a_c253d. This plugin does not reject the @GroovyASTTransformationClass annotation, allowing attackers with permission to define and run sandboxed scripts, including Pipelines, to run an arbitrary AST transformation at compile time. This bypasses the sandbox protection and executes arbitrary code in the context of the Jenkins controller JVM.

Vendor
Jenkins Project
Product
Jenkins Script Security Plugin
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-21
Advisory published
2026-09-16
Advisory updated
2026-09-21

Who should care

Jenkins administrators and users with permission to define and run sandboxed scripts should assess exposure and apply remediation. They should also review and restrict permissions for users who can define and run sandboxed scripts, and monitor Jenkins controller JVM for suspicious activity.

Why it matters

CVE-2026-92125 allows attackers with script permissions to execute arbitrary code, bypassing sandbox protections. Defenders should verify exposure, restrict script permissions, and monitor for suspicious activity.

  • Potential code execution in the context of the Jenkins controller JVM
  • Bypass of sandbox protection for scripts
  • Elevation of privileges for attackers with script permissions

Technical summary

The Jenkins Script Security Plugin is vulnerable to arbitrary AST transformation execution. Attackers with permission to define and run sandboxed scripts can bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM. This is due to the plugin not rejecting the @GroovyASTTransformationClass annotation. The vulnerability affects Jenkins Script Security Plugin versions up to 1415.v9a_f9b_3a_c253d. Defenders should prioritize verifying exposure and applying remediation for Jenkins Script Security Plugin versions up to 1415.v9a_f9b_3a_c253d.

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. The vulnerability allows attackers with script permissions to execute arbitrary code, bypassing sandbox protections. Defenders should verify exposure, restrict script permissions, and monitor for suspicious activity.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-92125 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-92125

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-92125 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92125

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.