# CVE-2026-70430: Code injection in Jenkins

> Attackers with management permissions can instantiate arbitrary types in project naming strategies, potentially leading to code execution or privilege escalation.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** BIT-jenkins-2026-70430, GHSA-xv7v-hw45-9jgw, MINI-66rr-4g93-jrjm, MINI-6c26-3hg5-3m6c, MINI-6jv7-fh6j-g958, MINI-cxqm-p4qc-992h, MINI-hr6j-9337-ccxm, MINI-mj69-rwjj-8m2g, MINI-pcfw-xjff-qvj8, MINI-r9q8-qp96-vmmp

## What is CVE-2026-70430?

CVE-2026-70430 is a low-severity code injection vulnerability in Jenkins Jenkins, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Jenkins 2.575 and earlier, LTS 2.568.1 and earlier does not restrict the types of objects that can be instantiated as part of the project naming strategy configuration, allowing attackers with Overall/Manage permission to instantiate arbitrary types related to configuration, including those intended for configuration only by administrators.

Weakness: CWE-284 (Improper Access Control)

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

1 open source package ship an affected version, including jenkins. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jenkins` | Bitnami | All versions | 2.568.2, 2.576.0 |

Products: Jenkins Jenkins.

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

Upgrade jenkins to a fixed version for your release line: 2.568.2 or 2.576.0.

## Is CVE-2026-70430 being exploited?

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

## Other vulnerabilities in Jenkins Jenkins

- [CVE-2024-23897](https://insights.sbomify.com/CVE-2024-23897/): Jenkins Command Line Interface (CLI) Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2018-1000861](https://insights.sbomify.com/CVE-2018-1000861/): Jenkins Stapler Web Framework Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2017-1000353](https://insights.sbomify.com/CVE-2017-1000353/): Jenkins Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-5317](https://insights.sbomify.com/CVE-2015-5317/): Jenkins User Interface (UI) Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2021-21690](https://insights.sbomify.com/CVE-2021-21690/): Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70430 is a low-severity code injection vulnerability in Jenkins Jenkins, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70430 in the wild and no public exploit code.

Affected packages and fixed versions:
- jenkins (Bitnami): affected all versions; fixed in 2.568.2, 2.576.0

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-70430/ (Markdown: https://insights.sbomify.com/CVE-2026-70430/index.md)
```

## Sources

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

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