Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-57281 high CVSS 7.5

Vulnerability in org.jenkins-ci.plugins:script-security (CVE-2026-57281)

Summary

Vulnerability in org.jenkins-ci.plugins:script-security (CVE-2026-57281). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1402.1405.vc96e74964250 or later.

Original description

The description as published by the source.

Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier does not reject Groovy AST transformation annotations such as @CompileStatic and @TypeChecked that carry an extensions member, which causes Groovy to load and execute a script from the classpath at compile time, before the sandbox is applied.

This may allow attackers able to define and run sandboxed scripts to execute code outside the sandbox, in the rare case that a suitable Groovy script is present on the classpath of the component that evaluates the script.

The Jenkins security team has been unable to identify any Groovy source files in Jenkins core or plugins that would allow attackers to execute dangerous code. While the severity of this issue is declared as High due to the potential impact, successful exploitation is considered very unlikely.

Script Security Plugin 1402.1405.vc96e74964250 rejects any annotation carrying an extensions member during sandbox compilation, before Groovy can resolve or execute the referenced script.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-57281 has been found in org.jenkins-ci.plugins:script-security.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade org.jenkins-ci.plugins:script-security to 1402.1405.vc96e74964250 or later.
If unsure, ask your IT team or search "org.jenkins-ci.plugins:script-security CVE-2026-57281" on the vendor's site.

CVE-2026-57281 (org.jenkins-ci.plugins:script-security) — CWE-93 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 1402.1405.vc96e74964250 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-93) exists in org.jenkins-ci.plugins:script-security.

📍 Affected scope

Check the vendor advisory for the affected versions of org.jenkins-ci.plugins:script-security.

🔥 Severity

Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1402.1405.vc96e74964250.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.jenkins-ci.plugins:script-security を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.jenkins-ci.plugins:script-security to 1402.1405.vc96e74964250

    ステージング環境で 1402.1405.vc96e74964250 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.jenkins-ci.plugins:script-security
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1402.1405.vc96e74964250"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details