Is CVE-2026-92129 exploited in the wild?

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

How severe is CVE-2026-92129?

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

Is there a fix for CVE-2026-92129?

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-92129 attacked?

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

Am I affected by CVE-2026-92129?

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-92129: Jenkins Script Security Plugin sandbox bypass with dynamic methods

CVE-2026-92129 · Severity: high · CVSS 7.5 · Published 2026-09-16

Jenkins Script Security Plugin provides a sandbox that lets administrators safely run user-supplied scripts and Pipelines without exposing the Jenkins server to malicious code. This vulnerability allows attackers with script authoring permissions to bypass the sandbox and execute arbitrary code with full Jenkins controller privileges by exploiting how the plugin handles methods added dynamically to classes at runtime, compromising the security of the entire Jenkins instance.

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

Quick answers

Is CVE-2026-92129 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92129 being exploited in the wild.
How severe is CVE-2026-92129?: High severity, with a CVSS score of 7.5, 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-92129?: 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-92129 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-92129?: 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 in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier. The plugin fails to intercept and validate calls to methods that are added dynamically to a class at runtime within sandboxed Groovy scripts. An attacker with permission to define and execute sandboxed scripts or Pipelines can leverage this gap to invoke unvetted dynamically-added methods that perform sensitive operations, bypassing the intended sandbox restrictions. The attack requires script authoring privileges on the Jenkins instance. The issue is resolved in version 1422.v06869826dd9b_ and later, which adds proper validation of dynamically-added method calls.

Affected products

Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier

Timeline

2026-09-16: disclosed
2026-09-16: other: CVSS score and CVE ID published

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.