# CVE-2026-84670: Deserialization in Jenkins Performance Plugin

> Attackers with Item/Configure permission can execute arbitrary code on the Jenkins controller via unsafe deserialization of cached performance reports.

- **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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-v45c-jr4p-q7x2

## What is CVE-2026-84670?

CVE-2026-84670 is a high-severity unsafe deserialization vulnerability in Jenkins Performance Plugin, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Performance Plugin 1015.v09ca_52b_3370e and earlier does not restrict the classes that can be instantiated when deserializing cached performance reports stored in the build directory on the Jenkins controller, allowing attackers with Item/Configure permission to execute arbitrary code on the Jenkins controller.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-84670 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84670 is a high-severity unsafe deserialization vulnerability in Jenkins Performance Plugin, 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-84670 in the wild and no public exploit code.

Affected product: Jenkins Performance 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-84670/ (Markdown: https://insights.sbomify.com/CVE-2026-84670/index.md)
```

## Sources

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

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