Is CVE-2026-92125 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92125 being exploited in the wild.

How severe is CVE-2026-92125?

High severity, with a CVSS score of 8.8, published 16 September 2026.

Which products and versions are affected?

Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier.

Is there a fix for CVE-2026-92125?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-92125 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-92125?

Check whether you run Jenkins Script Security Plugin or Jenkins Script Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-92125: Jenkins Script Security Plugin sandbox bypass via @GroovyASTTransformationClass

CVE-2026-92125 · Severity: high · CVSS 8.8 · Published 2026-09-16

Jenkins Script Security Plugin is a sandboxing feature that allows running user-provided scripts safely by restricting dangerous operations. A vulnerability in versions 1415 and earlier allows attackers with permission to define and run scripts (including Pipelines) to bypass this sandbox protection entirely by using the @GroovyASTTransformationClass annotation, leading to arbitrary code execution on the Jenkins controller with full JVM privileges.

Technologies: Jenkins Script Security Plugin, Jenkins Script Security. Vendors: Jenkins.

Quick answers

Is CVE-2026-92125 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92125 being exploited in the wild.
How severe is CVE-2026-92125?: High severity, with a CVSS score of 8.8, published 16 September 2026.
Which products and versions are affected?: Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier.
Is there a fix for CVE-2026-92125?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-92125 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-92125?: Check whether you run Jenkins Script Security Plugin or Jenkins Script Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a sandbox bypass caused by insufficient validation of the @GroovyASTTransformationClass annotation during script compilation. An attacker can declare an annotation type linked to an arbitrary AST transformation via this annotation, causing Groovy to execute that transformation at compile time—before the sandbox is applied. This allows arbitrary code execution in the Jenkins controller JVM context. The attack requires the attacker to already have permission to define and run sandboxed scripts. The fix (Script Security Plugin 1422.v06869826dd9b_) rejects the @GroovyASTTransformationClass annotation during sandbox compilation, preventing Groovy from resolving or executing the referenced transformation.

Affected products

Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier

Timeline

2026-09-16: disclosed: Jenkins Security Advisory published
2026-09-16: other: Fixed in Script Security Plugin 1422.v06869826dd9b_

References

https://www.jenkins.io/security/advisory/2026-09-16/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.