Script SecurityApplication · Jenkins
CVE-2026-57280
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Script Security Plugin 1402.v94c9ce464861 and earlier does not intercept the implicit type casts applied to the elements of typed for-each loops in sandboxed Groovy scripts, allowing attackers able to provide such scripts to invoke arbitrary constructors and bypass the sandbox protection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins Script Security Plugin versions 1402.v94c9ce464861 and earlier fail to intercept implicit type casts applied to elements of typed for-each loops in sandboxed Groovy scripts. This allows attackers with the ability to provide sandboxed scripts to bypass sandbox protection and invoke arbitrary constructors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Script SecurityApplication
<= 1402.v94c9ce464861CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Jenkins Script Security Plugin versionNavigate to Jenkins Manage Plugins > Installed tab, or check the plugin's manifest file in the jenkins home directory under plugins/script-security/Affected if The installed version is 1402.v94c9ce464861 or earlier
-
Confirm Script Security sandbox is in useReview job configurations and pipeline definitions to see if sandboxed script execution is enabled (Groovy sandbox checkbox or @Grab annotations are used)Affected if Sandboxed script execution is enabled and untrusted scripts can be submitted
-
Check for Script Security API usage in scriptsInspect any Groovy scripts, pipelines, or job configs for typed for-each loops with implicit type casting syntax (e.g., for(String s in list))Affected if Typed for-each loops with implicit casts exist in sandboxed scripts
-
Review script submission permissionsVerify which users or groups have the ability to create or modify sandboxed scripts via job configurations, pipeline scripts, or Groovy system scriptsAffected if Users with untrusted or limited permissions can submit or modify sandboxed scripts
You are affected if the Jenkins Script Security Plugin version is 1402.v94c9ce464861 or earlier AND sandboxed scripts with typed for-each loops can be submitted by users who are not fully trusted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Jenkins Script Security Plugin to a version newer than 1402.v94c9ce464861 when available. Until then, restrict script submission permissions to trusted users only.
Fix this in Script Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57280 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data