# CVE-2026-84645: Code injection in Jenkins

> Attackers can achieve remote code execution by submitting malicious config.xml documents that exploit improper handling of nested configuration objects in Jenkins.

- **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:** Yes
- **Published:** 2 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** BIT-jenkins-2026-84645, GHSA-g5fg-fmcm-8xx6, MINI-263h-f586-7ccx, MINI-4q59-jp2m-h43p, MINI-8fj9-v9cm-qf94, MINI-99g3-x9mh-cmmv, MINI-jvqj-6p4q-cpv5, MINI-mhp4-p9g3-7jp4, MINI-qw72-hjqm-j366

## What is CVE-2026-84645?

CVE-2026-84645 is a high-severity code injection vulnerability in Jenkins Jenkins, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Jenkins 2.579 and earlier, LTS 2.568.2 and earlier, objects of types marked as storing their configuration in independent top-level configuration files in Jenkins (such as the global configuration and jobs) can appear as nested field values in user-submitted `config.xml` documents and subsequently handle HTTP requests via Stapler, resulting in remote code execution.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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

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.3, 2.580.0 |

Products: Jenkins Jenkins.

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

Upgrade jenkins to a fixed version for your release line: 2.568.3 or 2.580.0.

## Is CVE-2026-84645 being exploited?

There is no known exploitation of CVE-2026-84645 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-84645 and fix it if it is affected.

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

Affected packages and fixed versions:
- jenkins (Bitnami): affected all versions; fixed in 2.568.3, 2.580.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-84645/ (Markdown: https://insights.sbomify.com/CVE-2026-84645/index.md)
```

## Sources

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

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