# CVE-2026-70431: Code injection in Jenkins Multijob Plugin

> Attackers with specific Jenkins permissions can execute arbitrary code on the controller via Groovy scripting in the Multijob Plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-vxm7-6w3j-gm87

## What is CVE-2026-70431?

CVE-2026-70431 is a high-severity code injection vulnerability in Jenkins Multijob Plugin, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Multijob Plugin 669.v9d96a_d9c71b_0 and earlier provides Groovy scripting features that do not integrate with Script Security Plugin, allowing attackers with Item/Create or Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

No fix has been published for CVE-2026-70431 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70431 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70431 is a high-severity code injection vulnerability in Jenkins Multijob Plugin, published on 5 Aug 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-70431 in the wild and no public exploit code.

Affected product: Jenkins Multijob Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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