# CVE-2026-42519: Jenkins Script Security Plugin: Missing permission checks allow enumeration of pending and approved classpaths

> Attackers with Overall/Read permission can enumerate pending and approved Script Security classpaths due to a missing permission check.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-p334-gfhq-c7w6, MINI-85g8-xm34-c397, MINI-8xwf-v6q3-9q7r, MINI-h5rj-gh9v-gjwp, MINI-hwcj-fm5c-4fw3, MINI-mq3m-h279-hx4f, MINI-q9hc-g7g5-42c6, MINI-v269-vvg2-hfc3

## What is CVE-2026-42519?

CVE-2026-42519 is a medium-severity missing authorization vulnerability in Jenkins Script Security Plugin, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins Script Security Plugin 1399.ve6a_66547f6e1 and earlier allows attackers with Overall/Read permission to enumerate pending and approved Script Security classpaths.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-42519?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:script-security. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:script-security` | Maven | All versions | 1402.v94c9ce464861 |
| `org.jenkins-ci.plugins:script-security` | Maven | All versions | 1402.v94c9ce464861 |

Products: Jenkins Script Security.

## How do I fix CVE-2026-42519?

Upgrade org.jenkins-ci.plugins:script-security to 1402.v94c9ce464861 or later.

## Is CVE-2026-42519 being exploited?

There is no known exploitation of CVE-2026-42519 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Script Security Plugin

- [CVE-2019-1003029](https://insights.sbomify.com/CVE-2019-1003029/): Jenkins Script Security Plugin Sandbox Bypass (critical 9.9, exploited in the wild)
- [CVE-2022-43401](https://insights.sbomify.com/CVE-2022-43401/): Sandbox bypass vulnerabilities in Jenkins Script Security Plugin and in Pipeline: Groovy Plugin (critical 9.9)
- [CVE-2022-43403](https://insights.sbomify.com/CVE-2022-43403/): Jenkins Script Security Plugin sandbox bypass vulnerability (critical 9.9)
- [CVE-2022-43404](https://insights.sbomify.com/CVE-2022-43404/): Sandbox bypass vulnerabilities in Jenkins Script Security Plugin and in Pipeline: Groovy Plugin (critical 9.9)
- [CVE-2020-2279](https://insights.sbomify.com/CVE-2020-2279/): Sandbox bypass vulnerability in Jenkins Script Security Plugin (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42519 and fix it if it is affected.

What it is: CVE-2026-42519 is a medium-severity missing authorization vulnerability in Jenkins Script Security Plugin, published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42519 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:script-security (Maven): affected all versions; fixed in 1402.v94c9ce464861
- org.jenkins-ci.plugins:script-security (Maven): affected all versions; fixed in 1402.v94c9ce464861

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42519/ (Markdown: https://insights.sbomify.com/CVE-2026-42519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42519
- OSV: https://osv.dev/vulnerability/CVE-2026-42519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42519/
Summaries are generated and may contain mistakes; the official description above is the record.