Quick answers
- Is CVE-2026-84659 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84659 being exploited in the wild.
- How severe is CVE-2026-84659?
- Medium severity, with a CVSS score of 4.3, published 2 September 2026.
- Which products and versions are affected?
- Jenkins Script Security Plugin 1412.v7737b_3405f86 and earlier.
- Is there a fix for CVE-2026-84659?
- 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-84659 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84659?
- 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 exists in a configuration method that controls the "Force the use of the sandbox globally in the system" setting in Jenkins Script Security Plugin versions 1412.v7737b_3405f86 and earlier. The method fails to enforce proper permission checks before allowing modifications to this security setting. An attacker can exploit this via Stapler's data binding mechanism, which performs reflective access to exposed methods and fields, to submit a crafted HTTP request that disables the sandbox feature. This requires network access to the Jenkins instance but no prior authentication. Once the sandbox is disabled, an attacker could potentially execute arbitrary Groovy code with Jenkins process privileges.
Affected products
- Jenkins Script Security Plugin 1412.v7737b_3405f86 and earlier
Timeline
- 2026-09-02: disclosed
- 2026-09-02: advisory